db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rick Hillegas <Richard.Hille...@Sun.COM>
Subject Re: [jira] Updated: (DERBY-499) Expose BOOLEAN datatype to end users
Date Mon, 21 Nov 2005 18:18:42 GMT
Hi Francois,

In ANSI, BOOLEAN columns can be nullable, just like other columns. So 
there are three values which a BOOLEAN column may take: true, false, and 
null. Think of ANSI BOOLEAN as java.lang.Boolean.

I'm afraid I'm confused about your confusion about the INSERT statement. 
How can I clarify this piece of code?

Thanks,
-Rick

Francois Orsini wrote:

> Hi Rick,
>
> For a column of type BOOLEAN and Nullable (if such thing allowed in 
> the first place), is the default value 'false' if value not specified 
> upon an INSERT DML? - Am assuming that the BOOLEAN datatype as defined 
> in ANSI cannot be null - just wondering? Maybe something to add to the 
> specs.
>
> Also, the INSERT statement in the specs looks a bit confusing (VALUES 
> clause having 'false' & 'true' specified (I understood what you were 
> trying to mean tho)...
>
> Thanks,
>
> --francois
>
> On 11/21/05, *Rick Hillegas* <Richard.Hillegas@sun.com 
> <mailto:Richard.Hillegas@sun.com>> wrote:
>
>     Hi Bryan,
>
>     Nope. This does not affect getBoolean() and setBoolean() on other
>     datatypes.
>
>     Cheers,
>     -Rick
>
>     Bryan Pendleton wrote:
>
>     >> I have attached a thin functional specification describing
>     expected
>     >> SQL and JDBC behavior for the re-enabled BOOLEAN datatype.
>     >
>     >
>     > Are there any changes to the way that ResultSet.getBoolean()
>     > and PreparedStatement.setBoolean() work for data types *other*
>     > than the boolean data type?
>     >
>     > thanks,
>     >
>     > bryan
>     >
>     >
>
>


Mime
View raw message