Return-Path:
Behavior Clarification After deleteRow, ResultSet will be positioned right before the next row=
for FORWARD ONLY updatable ResultSets. Behavior Clarification After updateRow, ResultSet will be positioned right before th next row =
for FORWARD ONLY updatable ResultSets. Behavior Clarification An ASCII character is defined as an eight bit character (range 0x00 to =
0xff), see CHAR() function definition by [JDBC3] in appendix C.2. On Types.BLOB columns returns a stream with identical contents to that =
returned by getBlob().getBinaryStream() on the same column if the BLOB valu=
e is not NULL. If the BLOB value is NULL then null is returned. Extensions On Types.BLOB columns returns a stream with identical contents to that =
returned by getBlob().getBinaryStream() on the same column if the BLOB valu=
e is not NULL. If the BLOB value is NULL then null is returned. Behavior Clarification For binary types (Types.BINARY, Types.VARBINARY, and Types.LONGVARBINAR=
Y, Types.BLOB) getString() the value is converted to a stream of characters=
as though it is encoded using UTF-16BE. On Types.BLOB columns supported with conversion as a binary type. Behavior Clarification For binary types (Types.BINARY, Types.VARBINARY, and Types.LONGVARBINAR=
Y, Types.BLOB) getString() returns String containing a two character hexade=
cimal representation for every byte in a non-null value. The two char=
acters are in the range ‘0’ – ‘9’ and ‘=
a’ – ‘f’. For NULL values, null is returned. Note, =
that this String does not match the contents of the stream returned by getA=
sciiStream or getCharacterStream on the same column. On Types.BLOB columns supported with conversion as a binary type. Not implemented, deprecated by [JDBC3]. Binary Column If a binary column has been set with the Java byte array containing fou=
rs bytes, byte[] data =3D {0x34, 0x87, 0xc2, 0x1f} then: Behavior Clarification If the pos (position) argument is greater than the length of the BLOB t=
hen an exception is thrown. This matches the semantics of the SQL SUBSTR fu=
nction. Behavior Clarification If the pattern argument has length zero, then the value of start argume=
nt will be returned. This matches the semantics of the SQL LOCATE function.=
Behavior Clarification If the pos (position) argument is greater than the length of the CLOB t=
hen an exception is thrown. This matches the semantics of the SQL SUBSTR fu=
nction. Behavior Clarification 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. Derby’s SQL DATE type represents a date in the form yyyy-mm-dd wi=
th no associated time zone information. A JDBC Date (java.sql.Date) by definition represents a point in time on=
a given date in a given time zone. [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. JDBC drivers are required to return java.sql.Date objects that are norm=
alized to 00:00 according to the required time zone. Applications are expected to pass in java.sql.Date instances that are n=
ormalized to 00:00 (see section 18.1.1 of [TUTORIAL3]). Derby does not require that the application’s java.sql.Date value=
is normalized to 00:00 according to the required time zone. In both cases no time zone information is stored with the SQL DATE valu=
e=2E Three different date formats are built into Derby. 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 y=
yyy-mm-dd. 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>
-
+
Derby’s SQL TIME type represents a time of day in the form hh:mm:=
ss with no associated time zone information. A JDBC Time (java.sql.Time) by definition represents a point in time on=
an unspecified day in a given time zone. Java.sql.Time extends java.util.date, so it includes a date. [JDBC3] in=
tends that the date stored in a java.sql.Time be Jan 1 1970, but this is no=
t enforced by the class. JDBC drivers are required to return java.sql.Time objects that are norm=
alized to Jan. 1 1970 according to the required time zone. Applications are expected to pass in java.sql.Time instances that are n=
ormalized to Jan. 1 1970. Derby does not require that the application’s java.sql.Time value=
be normalized to Jan 1 1970 according to the required time zone. In both cases no time zone information is stored with the SQL TIME valu=
e=2E Three different time formats are built into Derby: 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 h=
h:mm:ss. 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>
-
+
Derby’s SQL TIMESTAMP type represents a time of day in the form y=
yyy-mm-dd hh:mm:ss.fffffffff (nanosecond granularity) with no associated ti=
me zone information. A JDBC Timestamp (java.sql.Timestamp) by definition represents a point =
in time, with nanosecond resolution, in a given time zone. Two different timestamp formats are built into Derby: If the format of the string matches one of the built in formats then a =
conversion to a java.sql.Timestamp matches that of a SQL TIMESTAMP value wi=
th value yyyy-mm-dd hh:mm:ss.ffffff. 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>
-Last Updated: January 17, 2005
+Last Updated: March 31, 2005
deleteRow()
updateRow()
+GetAsciiStream()
GetBinaryStream()
GetCharacterStream()
GetString()
GetUnicodeStream()
Examples
java.sql.Blob
getBytes(int pos, int length)
position(byte pattern, int start) andand position(Blob=
pattern, int start)
java.sql.Clob
getSubString(int pos, int length)
position(String searchstr, int start) andposition(Clob=
searchstr, int start)
Date Handling
Derby SQL DATE
java.sql.Date
Conversion of a JDBC java.sql.Date to a Derby DATE value
Conversion of a Derby DATE value to a JDBC java.sql.Date
-
+
Conversion of a string type to a JDBC java.sql.Date
@@ -522,16 +529,16 @@
Derby SQL TIME
java.sql.Time
Conversion of a JDBC java.sql.Time to a Derby TIME value
Conversion of a Derby TIME value to a JDBC java.sql.Time
-
+
Conversion of a string type to a JDBC java.sql.Time
@@ -604,13 +611,13 @@
Derby SQL TIMESTAMP
java.sql.Timestamp
Conversion of a JDBC java.sql.Timestamp to a Derby TIMESTAMP value
-
+
Conversion of a Derby TIMESTAMP value to a JDBC java.sql.Timestamp
-
+
Conversion of a string type to a JDBC java.sql.Timestamp
@@ -680,7 +687,7 @@
Behavior Clarification
++After updateRow, ResultSet will be positioned right before th next row for= FORWARD ONLY updatable ResultSets.=20 +
+Behavior Clarification
An ASCII character is defined as an eight bit character (range @@ -474,6 +481,6 @@ attempts to use the Java locale specific parser to interpret the string as a date.=20
-Last Updated: January 17, 2005
+Last Updated: March 31, 2005