empire-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rainer Döbele (JIRA) <empire-db-...@incubator.apache.org>
Subject [jira] [Closed] (EMPIREDB-46) datetime-phrase issue in DBDatabaseDriverDerby
Date Mon, 04 Feb 2013 14:08:12 GMT

     [ https://issues.apache.org/jira/browse/EMPIREDB-46?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Rainer Döbele closed EMPIREDB-46.
---------------------------------


Cleanup of unclosed issues.
                
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message