Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
Release Note Needed
Description
There exists difference of type compatibility between Embedded and NetworkServer/NetworkClient.
This issue tries to resolve it.
Attachments
Attachments
Issue Links
- blocks
-
DERBY-1535 Trial 2 for DERBY-550, improve use of Engine from NetworkServer and reduce memory usage
- Closed
-
DERBY-1559 when receiving a single EXTDTA object representing a BLOB, the server do not need to read it into memory before inserting it into the DB
- Closed
-
DERBY-550 BLOB : java.lang.OutOfMemoryError with network JDBC driver (org.apache.derby.jdbc.ClientDriver)
- Closed
- incorporates
-
DERBY-2704 There exists difference of handling NULL value in getXXXXStream/getBlob/getClob methods between Embedded and NetworkClient/Server
- Open
-
DERBY-1501 PreparedStatement#setNull(int parameterIndex, int sqlType) throws SQL Exception if given sqlType is LONGVARBINARY in embedded mode
- Closed
-
DERBY-1494 PreparedStatement.setNull(int, int) checks type compatibility on embedded, but not on the client
- Closed
- is part of
-
DERBY-310 Document and/or change Derby client code to match behavior with Embedded driver where possible.
- Closed
- is related to
-
DERBY-1904 COALESCE with NULL parameter problem
- Closed
-
DERBY-1942 There exists difference between behavior of setNull(Types.TIME) and setTiime(null).
- Closed
-
DERBY-1938 Add support for setObject(<arg>, null)
- Closed
-
DERBY-2743 Run 10.2 tests against 10.3 and evaluate to identify incompatibilities
- Closed
- relates to
-
DERBY-2430 setObject(int targetType, Blob source) and setObject(int targetType, Clob source) should disallow updates on all targetTypes except BLOB and CLOB respectively
- Closed