db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jean T. Anderson (JIRA)" <derby-...@db.apache.org>
Subject [jira] Resolved: (DERBY-234) Documentation of DateTime types is incomplete
Date Thu, 05 May 2005 03:52:06 GMT
     [ http://issues.apache.org/jira/browse/DERBY-234?page=all ]
     
Jean T. Anderson resolved DERBY-234:
------------------------------------

    Resolution: Fixed

Patch applied and committed revision 168252.

> Documentation of DateTime types is incomplete
> ---------------------------------------------
>
>          Key: DERBY-234
>          URL: http://issues.apache.org/jira/browse/DERBY-234
>      Project: Derby
>         Type: Bug
>   Components: Documentation
>     Versions: 10.0.2.0
>     Reporter: Jack Klebanoff
>     Priority: Minor
>  Attachments: derby234.diff
>
> The documentation for datatypes DATE, TIME, and TIMESTAMP is incomplete. The documentation
says that DATE, TIME, and TIMESTAMP accept any values accepted by the java.sql.Date, java.sql.Time,
and java.sql.Timestamp classes respectively. Derby accepts a number of string formats:
> DATE:
>   yyyy-mm-dd
>   mm/dd/yyyy
>   dd.mm.yyyy
> TIME:
>   hh:mm[:ss]
>   hh.mm[.ss]
>   hh[:mm] {AM | PM}
> TIMESTAMP:
>   yyyy-mm-dd-hh[.mm[.ss[.nnnnnn]]]
>   yyyy-mm-dd hh[:mm[:ss[.nnnnnn]]]
> The year must always have 4 digits. Months, days, and hours may have one or two digits.
Minutes and seconds, if present, must have two digits. Nanoseconds, if present may have 1
to 6 digits.
> Derby also accepts strings in the locale specific datetime format, using the locale of
the database server. If there is an ambiguity the built in formats above take precedence.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message