[DERBY-1029] Backout boolean work from the 10.2 branch immediately after the branch is created

• Type: Sub-task
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 10.2.1.6
• Fix Version/s: 10.2.1.6
• Component/s: SQL
• Assignee: Richard N. Hillegas
• Reporter: Katherine Marsden
• Created: 23/Feb/06 02:32
• Updated: 07/Aug/06 14:12
• Resolved: 21/Jul/06 18:57

Description

There was discussion on the list regarding how to handle this issue but keep the BOOLEAN work for inclusion in future releases. The approach discussed was to back the DERBY-499 work out of the 10.2 branch as soon as it is created, but leave it in the trunk

I think this an acceptable solution but only if we can get someone assigned to this issue that is willing to commit now to doing that work as soon as we branch. The reverse merge may be messy at that point do to other changes that have gone in.

Is there someone who will volunteer to do this work and assign themselves to this issue?

Issue Links

• is related to: DERBY-887 Select statement returns wrong number of rows if you compare an integer column with a boolean expression in the where clause
• is related to: DERBY-499 Expose BOOLEAN datatype to end users