The BOOLEAN datatype is also supported by Cloudscape 3.5 (which I
thought was an ancestor of Derby) and by the current Cloudscape 5.1.
Could someone at IBM do a little codeline archeology:
1What defects were logged against this datatype?
2) What bugfixes do we need to apply to Derby?
Thanks,
-Rick
Lance J. Andersen wrote:
Satheesh, can you provide an example WRT JDBC metadata as I do not
see an issue there.
more DB info:
Sybase ASE and IAnywhere do not support boolean, you can use bit.
Pointbase supports BOOLEAN
Daffodil supports BOOLEAN
MySQL 4.1 and beyond supports BOOLEAN as a TINYINT(1), that is it s a
synonym
Derby should have the support externally visible.
Regards
Lance
Satheesh Bandaram wrote:
I don't think all the support is there... Like using them in expressions
or JDBC metadata to name some.
Dan has a good point in the second link provided by Kathey. Here is the
current status of BOOLEAN support in other DBs, from that message:
IBM DB2 UDB 7/8 - not supported
Informix - BOOLEAN supported
MySQL 4.0 - not supported
Oracle 9/10 - not supported
Postgres 7.4 - BOOLEAN supported
SQL Server 2000 - not supported
Satheesh
Francois Orsini wrote:
Boolean column type is ANSI SQL-99 - if support is already there and
assuming there is no known issues (none in JIRA at least), then it
would be good to see it back from the grave. Just IMHO.
On 8/8/05, Kathey Marsden <[EMAIL PROTECTED]> wrote:
Rick Hillegas wrote:
Hi Slavic,
Thanks for bringing up this issue. Derby internally supports boolean
types but does not let users declare boolean typed columns. I have
logged an enhancment request (499) to track this issue. For the
moment, you can kludge around this problem by creating columns of type
CHAR(1).
Maybe SMALLINT would be a good option for use with getBoolean(). A
value of 1 will return true.
Here are two relevant mails on this issue:
http://mail-archives.apache.org/mod_mbox/db-derby-user/200412.mbox/[EMAIL
PROTECTED]
http://mail-archives.apache.org/mod_mbox/db-derby-user/200412.mbox/[EMAIL
PROTECTED]
