|
This issue incorporates:
|
|
|
DERBY-2992 getBinaryStream returns incorrect result (truncated value) if underlying blob is deleted
|
|
|
|
 |
|
DERBY-1030 In some situations a RETURNS NULL ON NULL function is called when one ot its parameters is NULL
|
|
|
|
|
|
|
DERBY-2017 Client driver can insert and commit partial data when a LOB stream throws IOException or does not match the specified length
|
|
|
|
|
|
|
DERBY-2602 TIMESTAMP value is truncated when return to client
|
|
|
|
|
|
DERBY-3231
Sorting on COUNT with OR and GROUP BY delivers wrong results.
|
|
|
|
|
|
DERBY-3061
Wrong results from query with two conjuncts
|
|
|
|
|
|
DERBY-3341
TABLE FUNCTION returning CHAR values does not return a correct value if the Java ResultSet class returns a value less than the length of the defined CHAR.
|
|
|
|
|
|
DERBY-3288
wrong query result in presence of a unique index
|
|
|
|
|
|
DERBY-3301
Incorrect result from query with nested EXIST
|
|
|
|
|
|
DERBY-3023
Different result rows depending on the sequence of INNER JOIN and OUTER JOIN
|
|
|
|
|
|
DERBY-1949
locate function documentation should clarify behavior when first parameter is empty string
|
|
|
|
|
|
DERBY-2105
Network Client - Column of type CHAR, VARCHAR or LONG VARCHAR contains wrong value after being updated using the updateObject() method with a clob as parameter.
|
|
|
|
|
|
DERBY-3257
SELECT with HAVING clause containing OR conditional incorrectly return 1 row - should return 2 rows - works correctly with 10.2 DB
|
|
|
|
|
|
DERBY-2526
Wrong results with queries that use the JOIN ... ON syntax to join with views or other non-base table expressions.
|
|
|
|
|
|
DERBY-2370
EXISTS may return the wrong value for sub-queries involving set operations
|
|
|
|
|
|
DERBY-2256
Wrong Results: Use of decimal values in an IN-list with INTEGER left operand can lead to extra rows.
|
|
|
|
|
|
DERBY-889
with client getTimestamp on a TIME column will print the date 1900-01-01 instead of the current date
|
|
|
|
|
|
DERBY-1852
Wrong results: duplicate rows returned for nested UNIONs when they should be eliminated.
|
|
|
|
|
|
DERBY-1231
LIKE does not match empty strings when used with a prepared statement
|
|
|
|
|
DERBY-1816
Client's ResultSet.getTime() on a SQL TIMESTAMP column loses the sub-second resolution and always has a milli-second value of zero.
|
|
|
|
Task
Trivial
