You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@empire-db.apache.org by "Francis De Brabandere (JIRA)" <em...@incubator.apache.org> on 2009/07/25 11:10:14 UTC
[jira] Resolved: (EMPIREDB-46) datetime-phrase issue in
DBDatabaseDriverDerby
[ https://issues.apache.org/jira/browse/EMPIREDB-46?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Francis De Brabandere resolved EMPIREDB-46.
-------------------------------------------
Resolution: Fixed
patch applied
> datetime-phrase issue in DBDatabaseDriverDerby
> ----------------------------------------------
>
> Key: EMPIREDB-46
> URL: https://issues.apache.org/jira/browse/EMPIREDB-46
> Project: Empire-DB
> Issue Type: Bug
> Affects Versions: empire-db-2.0.5-incubating
> Reporter: Francis De Brabandere
> Assignee: Francis De Brabandere
> Fix For: empire-db-2.0.5-incubating
>
>
> Eike Kettner to empire-db-dev
> I found a small bug in DBDatabaseDriverDerby. The phrase for obtaining
> the current date-time is specified as "NOW()". The Derby doc says to
> use CURRENT_TIMESTAMP. I have tried this a minute ago and it worked
> for me.
> DBDatabaseDriverDerby (195):
> -case SQL_CURRENT_DATETIME: return "NOW()";
> +case SQL_CURRENT_DATETIME: return "CURRENT_TIMESTAMP";
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.