db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel John Debrunner <...@debrunners.com>
Subject Re: [jira] Updated: (DERBY-499) Expose BOOLEAN datatype to end users
Date Tue, 22 Nov 2005 04:08:49 GMT
Rick Hillegas (JIRA) wrote:
>      [ http://issues.apache.org/jira/browse/DERBY-499?page=all ]
> Rick Hillegas updated DERBY-499:
> --------------------------------
>     Attachment: BooleanFS.html
> I have attached a thin functional specification describing expected SQL and JDBC behavior
for the re-enabled BOOLEAN datatype.

Nice enhancment for Derby, I have some comments, most are related to
clarifying what you are intending to do.

Derby has never supported BOOLEAN, so you are not re-enabling it. This
might confuse readers of this spec.

In order to support BOOLEAN data type according to SQL Standard 2003
(feature T031) boolean literals need to be supported, and <boolean
literal> includes UNKNOWN

In the JDBC api section, I assume it means that this "In all other
cases, DatabaseMetaData and ResultSetMetaData will report BOOLEAN
columns as JDBC type java.sql.Types.SMALLINT." means the JDBC typid
column will be Types.SMALLINT, but the SQL type name will continue to be
BOOLEAN. E.g. ResultSetMetaData.getColumnNameType() will return
"BOOLEAN". Why Types.SMALLINT, and not Types.OTHER or Types.BIT?

Can I also assume you meant "ResultSet.getXXX and
CallableStatement.getXXX" methods?

When you say "... getXXX ... setXXX methods will succeed", what exactly
does that mean? How do the BOOLEAN values true and false map the
numeric/string getXXX values, and how do numeric/string values map to
true/false on the setXXX methods?

"methods will succeed on BOOLEAN columns peeked and poked by Derby 10.2
clients running on jdk1.4 or higher"
Can I retrieve/set BOOLEAN values on other clients?

Are you planning to support getObject/setObject?


View raw message