db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j..@apache.org
Subject svn commit: r292821 - /db/derby/site/trunk/build/site/papers/JDBCImplementation.html
Date Fri, 30 Sep 2005 17:55:51 GMT
Author: jta
Date: Fri Sep 30 10:55:50 2005
New Revision: 292821

URL: http://svn.apache.org/viewcvs?rev=292821&view=rev
Log:
Tomohito Nakayama committed a change to 
src/documentation/content/xdocs/papers/JDBCImplementation.html 
in revision 292415.  The log message for his commit was:
DERBY-525 - getAsciiStreamshould replace non-ASCII characters with 0x3f, '?' to match embedded
- Patch by Tomohito Nakayama (tomonaka@basil.ocn.ne.jp)

This commits the built page under build/site/papers/JDBCImplementation.html.


Modified:
    db/derby/site/trunk/build/site/papers/JDBCImplementation.html

Modified: db/derby/site/trunk/build/site/papers/JDBCImplementation.html
URL: http://svn.apache.org/viewcvs/db/derby/site/trunk/build/site/papers/JDBCImplementation.html?rev=292821&r1=292820&r2=292821&view=diff
==============================================================================
--- db/derby/site/trunk/build/site/papers/JDBCImplementation.html (original)
+++ db/derby/site/trunk/build/site/papers/JDBCImplementation.html Fri Sep 30 10:55:50 2005
@@ -358,11 +358,12 @@
 <p>On Types.BLOB columns returns a stream with identical contents to that returned
by getBlob().getBinaryStream() on the same column if the BLOB value is not NULL. If the BLOB
value is NULL then null is returned.</p>
 </li>
 </ul>
-<a name="N1009C"></a><a name="GetBinaryStream%28%29"></a>
+<p>This method is not recommended to use in Derby.<br>Because Derby handles characters
as unicode internally , there is no advantage in using this method .</p>
+<a name="N100A0"></a><a name="GetBinaryStream%28%29"></a>
 <h3 class="boxed">GetBinaryStream()</h3>
 <p>Extensions</p>
 <p>On Types.BLOB columns returns a stream with identical contents to that returned
by getBlob().getBinaryStream() on the same column if the BLOB value is not NULL. If the BLOB
value is NULL then null is returned.</p>
-<a name="N100A4"></a><a name="GetCharacterStream%28%29"></a>
+<a name="N100A8"></a><a name="GetCharacterStream%28%29"></a>
 <h3 class="boxed">GetCharacterStream()</h3>
 <p>Behavior Clarification</p>
 <p>For binary types (Types.BINARY, Types.VARBINARY, and Types.LONGVARBINARY, Types.BLOB)
getString() the value is converted to a stream of characters as though it is encoded using
UTF-16BE.</p>
@@ -377,7 +378,7 @@
 <p>On Types.BLOB columns supported with conversion as a binary type.</p>
 </li>
 </ul>
-<a name="N100B6"></a><a name="GetString%28%29"></a>
+<a name="N100BA"></a><a name="GetString%28%29"></a>
 <h3 class="boxed">GetString()</h3>
 <p>Behavior Clarification</p>
 <p>For binary types (Types.BINARY, Types.VARBINARY, and Types.LONGVARBINARY, Types.BLOB)
getString() returns String containing a two character hexadecimal representation for every
byte in a non-null value.&nbsp; The two characters are in the range &lsquo;0&rsquo;
&ndash; &lsquo;9&rsquo; and &lsquo;a&rsquo; &ndash; &lsquo;f&rsquo;.
For NULL values, null is returned. Note, that this String does not match the contents of the
stream returned by getAsciiStream or getCharacterStream on the same column.</p>
@@ -392,10 +393,10 @@
 <p>On Types.BLOB columns supported with conversion as a binary type.</p>
 </li>
 </ul>
-<a name="N100C8"></a><a name="GetUnicodeStream%28%29"></a>
+<a name="N100CC"></a><a name="GetUnicodeStream%28%29"></a>
 <h3 class="boxed">GetUnicodeStream()</h3>
 <p>Not implemented, deprecated by [JDBC3].</p>
-<a name="N100CE"></a><a name="Examples"></a>
+<a name="N100D2"></a><a name="Examples"></a>
 <h3 class="boxed">Examples</h3>
 <p>Binary Column</p>
 <p>If a binary column has been set with the Java byte array containing fours bytes,
byte[] data = {0x34, 0x87, 0xc2, 0x1f} then:</p>
@@ -424,43 +425,43 @@
 </ul>
 </div>
 </div>
-<a name="N100EB"></a><a name="java.sql.Blob"></a>
+<a name="N100EF"></a><a name="java.sql.Blob"></a>
 <h2 class="boxed">java.sql.Blob</h2>
 <div class="section">
-<a name="N100EF"></a><a name="getBytes%28int+pos%2C+int+length%29"></a>
+<a name="N100F3"></a><a name="getBytes%28int+pos%2C+int+length%29"></a>
 <h3 class="boxed">getBytes(int pos, int length)</h3>
 <p>Behavior Clarification</p>
 <p>If the pos (position) argument is greater than the length of the BLOB then an exception
is thrown. This matches the semantics of the SQL SUBSTR function.</p>
-<a name="N100F7"></a><a name="position%28byte+pattern%2C+int+start%29+and+position%28Blob+pattern%2C+int+start%29"></a>
+<a name="N100FB"></a><a name="position%28byte+pattern%2C+int+start%29+and+position%28Blob+pattern%2C+int+start%29"></a>
 <h3 class="boxed">position(byte pattern, int start) and position(Blob pattern, int
start)</h3>
 <p>Behavior Clarification</p>
 <p>If the pattern argument has length zero, then the value of start argument will be
returned. This matches the semantics of the SQL LOCATE function.</p>
 </div>
-<a name="N100FF"></a><a name="java.sql.Clob"></a>
+<a name="N10103"></a><a name="java.sql.Clob"></a>
 <h2 class="boxed">java.sql.Clob</h2>
 <div class="section">
-<a name="N10103"></a><a name="getSubString%28int+pos%2C+int+length%29"></a>
+<a name="N10107"></a><a name="getSubString%28int+pos%2C+int+length%29"></a>
 <h3 class="boxed">getSubString(int pos, int length)</h3>
 <p>Behavior Clarification</p>
 <p>If the pos (position) argument is greater than the length of the CLOB then an exception
is thrown. This matches the semantics of the SQL SUBSTR function.</p>
-<a name="N1010B"></a><a name="position%28String+searchstr%2C+int+start%29+and"></a>
+<a name="N1010F"></a><a name="position%28String+searchstr%2C+int+start%29+and"></a>
 <h3 class="boxed">position(String searchstr, int start) andposition(Clob searchstr,
int start)</h3>
 <p>Behavior Clarification</p>
 <p>If the searchstr argument has length zero (the empty string), then the value of
start argument will be returned. This matches the semantics of the SQL LOCATE function.</p>
 </div>
-<a name="N10115"></a><a name="Date+Handling"></a>
+<a name="N10119"></a><a name="Date+Handling"></a>
 <h2 class="boxed">Date Handling</h2>
 <div class="section">
-<a name="N10119"></a><a name="Derby+SQL+DATE"></a>
+<a name="N1011D"></a><a name="Derby+SQL+DATE"></a>
 <h3 class="boxed">Derby SQL DATE</h3>
 <p>Derby&rsquo;s SQL DATE type represents a date in the form yyyy-mm-dd with no
associated time zone information.</p>
-<a name="N1011F"></a><a name="java.sql.Date"></a>
+<a name="N10123"></a><a name="java.sql.Date"></a>
 <h4>java.sql.Date</h4>
 <p>A JDBC Date (java.sql.Date) by definition represents a point in time on a given
date in a given time zone.</p>
 <p>[JDBC3] intends that the point in time for a java.sql.Date object is 00:00 (midnight),
but this is not enforced by the class.</p>
 <p>JDBC drivers are required to return java.sql.Date objects that are normalized to
00:00 according to the required time zone.</p>
 <p>Applications are expected to pass in java.sql.Date instances that are normalized
to 00:00 (see section 18.1.1 of [TUTORIAL3]).</p>
-<a name="N1012B"></a><a name="Conversion+of+a+JDBC+java.sql.Date+to+a+Derby+DATE+value"></a>
+<a name="N1012F"></a><a name="Conversion+of+a+JDBC+java.sql.Date+to+a+Derby+DATE+value"></a>
 <h4>Conversion of a JDBC java.sql.Date to a Derby DATE value</h4>
 <ol>
 <li>
@@ -491,7 +492,7 @@
 </ol>
 <p>Derby does not require that the application&rsquo;s java.sql.Date value is normalized
to 00:00 according to the required time zone.</p>
 <p>In both cases no time zone information is stored with the SQL DATE value.</p>
-<a name="N10153"></a><a name="Conversion+of+a+Derby+DATE+value+to+a+JDBC+java.sql.Date"></a>
+<a name="N10157"></a><a name="Conversion+of+a+Derby+DATE+value+to+a+JDBC+java.sql.Date"></a>
 <h4>Conversion of a Derby DATE value to a JDBC java.sql.Date</h4>
 <ol>
 <li>
@@ -517,7 +518,7 @@
 </ul>
 </li>
 </ol>
-<a name="N1016C"></a><a name="Conversion+of+a+string+type+to+a+JDBC+java.sql.Date"></a>
+<a name="N10170"></a><a name="Conversion+of+a+string+type+to+a+JDBC+java.sql.Date"></a>
 <h4>Conversion of a string type to a JDBC java.sql.Date</h4>
 <p>Three different date formats are built into Derby.</p>
 <div style="margin-left: 2em">
@@ -535,16 +536,16 @@
 </div>
 <p>If the format of the string matches one of the built in formats then a conversion
to a java.sql.Date matches that of a SQL DATE value with value yyyy-mm-dd.</p>
 <p>If the string does not match any of the built in formats Derby attempts to use the
Java locale specific parser to interpret the string as a date.</p>
-<a name="N10182"></a><a name="Derby+SQL+TIME"></a>
+<a name="N10186"></a><a name="Derby+SQL+TIME"></a>
 <h3 class="boxed">Derby SQL TIME</h3>
 <p>Derby&rsquo;s SQL TIME type represents a time of day in the form hh:mm:ss with
no associated time zone information.</p>
-<a name="N10188"></a><a name="java.sql.Time"></a>
+<a name="N1018C"></a><a name="java.sql.Time"></a>
 <h4>java.sql.Time</h4>
 <p>A JDBC Time (java.sql.Time) by definition represents a point in time on an unspecified
day in a given time zone.</p>
 <p>Java.sql.Time extends java.util.date, so it includes a date. [JDBC3] intends that
the date stored in a java.sql.Time be Jan 1 1970, but this is not enforced by the class.</p>
 <p>JDBC drivers are required to return java.sql.Time objects that are normalized to
Jan. 1 1970 according to the required time zone.</p>
 <p>Applications are expected to pass in java.sql.Time instances that are normalized
to Jan. 1 1970.</p>
-<a name="N10194"></a><a name="Conversion+of+a+JDBC+java.sql.Time+to+a+Derby+TIME+value"></a>
+<a name="N10198"></a><a name="Conversion+of+a+JDBC+java.sql.Time+to+a+Derby+TIME+value"></a>
 <h4>Conversion of a JDBC java.sql.Time to a Derby TIME value</h4>
 <ol>
 <li>
@@ -575,7 +576,7 @@
 </ol>
 <p>Derby does not require that the application&rsquo;s java.sql.Time value be normalized
to Jan 1 1970 according to the required time zone.</p>
 <p>In both cases no time zone information is stored with the SQL TIME value.</p>
-<a name="N101BC"></a><a name="Conversion+of+a+Derby+TIME+value+to+a+JDBC+java.sql.Time"></a>
+<a name="N101C0"></a><a name="Conversion+of+a+Derby+TIME+value+to+a+JDBC+java.sql.Time"></a>
 <h4>Conversion of a Derby TIME value to a JDBC java.sql.Time</h4>
 <ol>
 <li>
@@ -601,7 +602,7 @@
 </ul>
 </li>
 </ol>
-<a name="N101D5"></a><a name="Conversion+of+a+string+type+to+a+JDBC+java.sql.Time"></a>
+<a name="N101D9"></a><a name="Conversion+of+a+string+type+to+a+JDBC+java.sql.Time"></a>
 <h4>Conversion of a string type to a JDBC java.sql.Time</h4>
 <p>Three different time formats are built into Derby:</p>
 <div style="margin-left: 2em">
@@ -619,13 +620,13 @@
 </div>
 <p>If the format of the string matches one of the built in formats then a conversion
to a java.sql.Time matches that of a SQL TIME value with value hh:mm:ss.</p>
 <p>If the string does not match any of the built in formats Derby attempts to use the
Java locale specific parser to interpret the string as a date.</p>
-<a name="N101EB"></a><a name="Derby+SQL+TIMESTAMP"></a>
+<a name="N101EF"></a><a name="Derby+SQL+TIMESTAMP"></a>
 <h3 class="boxed">Derby SQL TIMESTAMP</h3>
 <p>Derby&rsquo;s SQL TIMESTAMP type represents a time of day in the form yyyy-mm-dd
hh:mm:ss.fffffffff (nanosecond granularity) with no associated time zone information.</p>
-<a name="N101F1"></a><a name="java.sql.Timestamp"></a>
+<a name="N101F5"></a><a name="java.sql.Timestamp"></a>
 <h4>java.sql.Timestamp</h4>
 <p>A JDBC Timestamp (java.sql.Timestamp) by definition represents a point in time,
with nanosecond resolution, in a given time zone.</p>
-<a name="N101F7"></a><a name="Conversion+of+a+JDBC+java.sql.Timestamp+to+a+Derby+TIMESTAMP+value"></a>
+<a name="N101FB"></a><a name="Conversion+of+a+JDBC+java.sql.Timestamp+to+a+Derby+TIMESTAMP+value"></a>
 <h4>Conversion of a JDBC java.sql.Timestamp to a Derby TIMESTAMP value</h4>
 <ol>
 <li>
@@ -654,7 +655,7 @@
 </ul>
 </li>
 </ol>
-<a name="N10223"></a><a name="Conversion+of+a+Derby+TIMESTAMP+value+to+a+JDBC+java.sql.Timestamp"></a>
+<a name="N10227"></a><a name="Conversion+of+a+Derby+TIMESTAMP+value+to+a+JDBC+java.sql.Timestamp"></a>
 <h4>Conversion of a Derby TIMESTAMP value to a JDBC java.sql.Timestamp</h4>
 <ol>
 <li>
@@ -680,7 +681,7 @@
 </ul>
 </li>
 </ol>
-<a name="N1023C"></a><a name="Conversion+of+a+string+type+to+a+JDBC+java.sql.Timestamp"></a>
+<a name="N10240"></a><a name="Conversion+of+a+string+type+to+a+JDBC+java.sql.Timestamp"></a>
 <h4>Conversion of a string type to a JDBC java.sql.Timestamp</h4>
 <p>Two different timestamp formats are built into Derby:</p>
 <div style="margin-left: 2em">



Mime
View raw message