db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-499) Expose BOOLEAN datatype to end users
Date Wed, 15 Feb 2006 01:02:12 GMT
    [ http://issues.apache.org/jira/browse/DERBY-499?page=comments#action_12366417 ] 

Kathey Marsden commented on DERBY-499:
--------------------------------------

Apparently there was a problem with my original mail going to the list so I will make a link
here.
http://issues.apache.org/jira/browse/DERBY-499#action_12366383

In Ricks response he said

>Let me punch up the importance of this point: Our own production code already >relies
on pre-existing illegal casts and comparisons. Quite likely, some of our customers do too.

Yes, this is one problem I am happy to defer to another day. It would only be exacerbated
now by allowing user-declarable BOOLEAN columns/args.


>In summary:

>o I think that we should back out user-declarable BOOLEAN columns/args one way or another.

great in svn merge  you can just reverse the order of change number to back out the patch,
but there may be conflicts due to intervening changes.

svn merge -r 1234:1233   https://svn.apache.org/repos/asf/db/derby/code/trunk

>o If (1) and (2) are showstoppers, they are showstoppers regardless of what we do about
user-declarable BOOLEAN columns/args.

I don't think so.  If we just leave it just like 10.1 is for now and think on this whole problem
a bit more for how to create a BOOLEAN type for 10.3.



> Expose BOOLEAN datatype to end users
> ------------------------------------
>
>          Key: DERBY-499
>          URL: http://issues.apache.org/jira/browse/DERBY-499
>      Project: Derby
>         Type: New Feature
>   Components: SQL
>     Versions: 10.1.1.0
>     Reporter: Rick Hillegas
>     Assignee: Rick Hillegas
>  Attachments: BooleanFS.html, bug499.diff, bug499_doc.zip, bug499_jdk13tests.diff, bug499_jdk13tests_rev2.diff,
bug499_rev2.diff, bug499_rev3.diff, bug499_rev4.diff, jdk131BooleanFailures.zip
>
> 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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message