[
https://issues.apache.org/jira/browse/DERBY-5451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13128177#comment-13128177
]
Lukas Eder commented on DERBY-5451:
-----------------------------------
Thanks for the explanation. I didn't realize the SQL standard was so
restrictive.
With jOOQ (http://www.jooq.org), I am currently running integration tests
against any of these 12 RDBMS:
- DB2
- Derby
- H2
- HSQLDB
- Ingres
- MySQL
- Oracle
- Postgres
- SQLite
- SQL Server
- Sybase ASE
- Sybase SQL Anywhere
Casting numeric types to boolean works in all RDBMS, except Derby and HSQLDB
(and Oracle, which doesn't have a boolean SQL type). So a slight deviation from
the standard might be worth thinking about.
> Allow for casting numeric types to BOOLEAN
> ------------------------------------------
>
> Key: DERBY-5451
> URL: https://issues.apache.org/jira/browse/DERBY-5451
> Project: Derby
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 10.8.1.2
> Reporter: Lukas Eder
> Priority: Minor
> Labels: cast, conversion, sql, syntax, type, typesystem
>
> According to the casting matrix:
> http://db.apache.org/derby/docs/10.8/ref/rrefsqlj33562.html
> it is currently not possible to write CAST(1 as BOOLEAN). At the same time,
> casting CHAR and VARCHAR as BOOLEAN is possible, e.g. CAST('1' as BOOLEAN),
> or CAST(CAST(1 as CHAR(1)) as BOOLEAN). This was recently implemented:
> https://issues.apache.org/jira/browse/DERBY-4658
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
