db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Francois Orsini <francois.ors...@gmail.com>
Subject Re: [jira] Updated: (DERBY-499) Expose BOOLEAN datatype to end users
Date Mon, 21 Nov 2005 17:47:16 GMT
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> 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