[DERBY-2034] Tracking of bugs that lead to incorrect results being stored or returned to the client

• Type: Task
• Status: Closed
• Priority: Trivial
• Resolution: Fixed
• Affects Version/s: 10.6.1.0
• Fix Version/s: 10.6.1.0
• Component/s: Miscellaneous
• Assignee: Unassigned
• Reporter: Daniel John Debrunner
• Created: 02/Nov/06 22:35
• Updated: 21/Jan/11 18:27
• Resolved: 17/Aug/09 10:51

Description

Just a placeholder to link bugs that cause an application to get incorrect data results.
Queries that fail to compile are not linked here as an application would notice such failures and not use the statement.

Issue Links

• incorporates: DERBY-3061 Wrong results from query with two conjuncts
• incorporates: DERBY-3231 Sorting on COUNT with OR and GROUP BY delivers wrong results.
• incorporates: DERBY-889 with client getTimestamp on a TIME column will print the date 1900-01-01 instead of the current date
• incorporates: DERBY-1030 In some situations a RETURNS NULL ON NULL function is called when one ot its parameters is NULL
• incorporates: DERBY-1231 LIKE does not match empty strings when used with a prepared statement
• incorporates: DERBY-1852 Wrong results: duplicate rows returned for nested UNIONs when they should be eliminated.
• incorporates: DERBY-1949 locate function documentation should clarify behavior when first parameter is empty string
• incorporates: DERBY-2017 Client driver can insert and commit partial data when a LOB stream throws IOException or does not match the specified length
• incorporates: 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.
• incorporates: DERBY-2256 Wrong Results: Use of decimal values in an IN-list with INTEGER left operand can lead to extra rows.
• incorporates: DERBY-2370 EXISTS may return the wrong value for sub-queries involving set operations
• incorporates: DERBY-2526 Wrong results with queries that use the JOIN ... ON syntax to join with views or other non-base table expressions.
• incorporates: DERBY-2992 getBinaryStream returns incorrect result (truncated value) if underlying blob is deleted
• incorporates: DERBY-3023 Different result rows depending on the sequence of INNER JOIN and OUTER JOIN
• incorporates: DERBY-3257 SELECT with HAVING clause containing OR conditional incorrectly return 1 row - should return 2 rows - works correctly with 10.2 DB
• incorporates: DERBY-3288 wrong query result in presence of a unique index
• incorporates: DERBY-3301 Incorrect result from query with nested EXIST
• incorporates: 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.
• incorporates: 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.
• incorporates: DERBY-2602 TIMESTAMP value is truncated when return to client