Hi, why locale of the database server? not user locale, if it's multi-user environement?
just asking, best regards, Slavic Jeff Levitt (JIRA) wrote: > [ http://issues.apache.org/jira/browse/DERBY-234?page=all ] > > Jeff Levitt updated DERBY-234: > ------------------------------ > > Attachment: derby234.diff > > This patch adds the missing documentation to the three datatypes. The > information and examples provided by Jack in this issue have been placed in > the DATE, TIME, and TIMESTAMP files accordingly. > > >>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. > >
