The grammar's datatype-declaration-production contains a line which
disables the BOOLEAN datatype. If you remove this line, you can
successfully create tables with BOOLEAN columns. You can even create
indexes on those columns. You can even fudge around the lack of TRUE and
FALSE literals by inserting 1 and 0 into the BOOLEAN columns.
Anyone know why the BOOLEAN datatype was explicitly disabled?
Thanks,
-Rick
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).
Cheers.
-Rick
Veaceslav Chicu wrote:
Hi,
no BOOLEAN type in derby?
Slavic
