[DERBY-499] Expose BOOLEAN datatype to end users

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.1.1.0
• Fix Version/s: 10.7.1.1
• Component/s: SQL
• Assignee: Unassigned
• Reporter: Richard N. Hillegas
• Created: 09/Aug/05 03:45
• Updated: 02/May/13 02:29
• Resolved: 29/Sep/10 17:49

Description

Veaceslav Chicu started an email thread on 8 August 2005 titled "boolean type". He was disappointed that Derby doesn't support the ansi BOOLEAN datatype. On closer inspection, Derby does internally support this type but does not expose this support to end users.

Derby should let users declare table columns of type BOOLEAN. This should be an indexable datatype.

Issue Links

• incorporates: DERBY-4583 TRUE by itself is not accepted in WHERE
• incorporates: DERBY-4684 Correct the implicit casting of other types to BOOLEAN
• incorporates: DERBY-4692 Unions between BOOLEAN and non-BOOLEAN datatypes should be rejected
• incorporates: DERBY-4704 Incorrect nullability when casting non-nullable VARCHAR to BOOLEAN
• incorporates: DERBY-4613 Make client driver treat BOOLEAN columns the same way as the embedded driver does.
• incorporates: DERBY-4657 Allow functions to return BOOLEAN values
• incorporates: DERBY-4658 Allow explicit casts of string values to BOOLEAN
• incorporates: DERBY-4659 Allow routines to take arguments of BOOLEAN type
• incorporates: DERBY-4703 Make it possible for table functions to return BOOLEAN columns
• incorporates: DERBY-4714 Clean up some edge-case uses of the BOOLEAN keyword
• incorporates: DERBY-4716 Enable BOOLEAN typed columns
• incorporates: DERBY-4720 Allow boolean-valued expressions in select lists
• incorporates: DERBY-4730 Add BOOLEAN to the list of datatypes returned by DatabaseMetaData.getTypeInfo()
• incorporates: DERBY-4737 Document the BOOLEAN datatype
• is blocked by: DERBY-887 Select statement returns wrong number of rows if you compare an integer column with a boolean expression in the where clause
• is depended upon by: DERBY-2651 Embedded and client behave differently for IJ command "show indexes"
• is related to: DERBY-4663 Write a regression test to verify the behavior of ResultSet.getBoolean()
• relates to: DERBY-1029 Backout boolean work from the 10.2 branch immediately after the branch is created