db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From chaa...@apache.org
Subject svn commit: r1310489 - /db/derby/docs/trunk/src/ref/rrefsqlj27620.dita
Date Fri, 06 Apr 2012 17:25:33 GMT
Author: chaase3
Date: Fri Apr  6 17:25:32 2012
New Revision: 1310489

URL: http://svn.apache.org/viewvc?rev=1310489&view=rev
Log:
DERBY-5596  TIMESTAMP doc gives wrong precision limitation

Corrected one Reference Manual topic.

Patch: DERBY-5596.diff

Modified:
    db/derby/docs/trunk/src/ref/rrefsqlj27620.dita

Modified: db/derby/docs/trunk/src/ref/rrefsqlj27620.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefsqlj27620.dita?rev=1310489&r1=1310488&r2=1310489&view=diff
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefsqlj27620.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefsqlj27620.dita Fri Apr  6 17:25:32 2012
@@ -28,20 +28,23 @@ It permits a fractional-seconds value of
 <refsyn><title>Syntax</title><codeblock><b>TIMESTAMP</b></codeblock>
</refsyn>
 <section><title>Corresponding compile-time Java type</title><p><i>java.sql.Timestamp</i></p>
</section>
 <section><title>JDBC metadata type (java.sql.Types)</title><p>TIMESTAMP</p><p>Dates,
-times, and timestamps cannot be mixed with one another in expressions.</p><p><ph
-conref="../conrefs.dita#prod/productshortname"></ph> supports the following
-formats for TIMESTAMP:<codeblock>yyyy-mm-dd hh:mm:ss[.nnnnnn]
-yyyy-mm-dd-hh.mm.ss[.nnnnnn]</codeblock>The first of the two formats above
-is the <i>java.sql.Timestamp</i> format.</p><p>The year must always
have four
+times, and timestamps cannot be mixed with one another in expressions.</p>
+<p><ph conref="../conrefs.dita#prod/productshortname"></ph> supports the
+following formats for TIMESTAMP:
+<codeblock>yyyy-mm-dd hh:mm:ss[.nnnnnnnnn]
+yyyy-mm-dd-hh.mm.ss[.nnnnnnnnn]</codeblock>
+The first of the two formats above is the <i>java.sql.Timestamp</i> format.</p>
+<p>The year must always have four
 digits. Months, days, and hours may have one or two digits. Minutes and seconds
 must have two digits. Nanoseconds, if present, may have between
-one and six digits.</p><p><ph conref="../conrefs.dita#prod/productshortname"></ph>
also
+one and nine digits.</p><p><ph conref="../conrefs.dita#prod/productshortname"></ph>
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.</p> </section>
 <example> <title>Examples</title><codeblock><b>VALUES '1960-01-01
23:03:20'
 VALUES TIMESTAMP('1962-09-23 03:23:34.234')
-VALUES TIMESTAMP('1960-01-01 23:03:20')</b></codeblock> </example>
+VALUES TIMESTAMP('1960-01-01 23:03:20')
+VALUES TIMESTAMP('1962-09-23-03:23:34.987654321')</b></codeblock> </example>
 </refbody>
 </reference>
 



Mime
View raw message