Hi guys
On 1 Mrz., 09:12, ipolevoy <
ipole...@gmail.com> wrote:
> Arafat, this is great, however keep in mind, that adding a new dialect
> also means passing entire test suite against is.
> Please, see that this is included.
> Also, Derby is a small Java DB, so, please add it as a test level
> dependency so that Maven build automatically pulls it in. In other
> words, the build must pass all tests against the Derby if you run it
> in a Derby profile - see how other databases are integrated in the pom
I'm following this a bit as I'm developing a database abstraction tool
that is similar to ActiveJDBC (
http://jooq.sourceforge.net). I can
tell you, that with the Derby database, you need to take extra care
about type-safety. Derby is a very strongly typed database. You will
need to explicitly type-cast many of your PreparedStatement
parameters. These things need to be reflected in all integration tests
compatibly with other SQL dialects.
An example: You might not be able to do things like
SELECT ? FROM SYSIBM.SYSDUMMY1
instead you have to write
SELECT cast(? as int) FROM SYSIBM.SYSDUMMY1
this is especially true when NULL values are involved, which have to
have a type attached as well:
SELECT cast(null as int) FROM SYSIBM.SYSDUMMY1
Just my two cents.
Have fun implementing! :-)
Cheers
Lukas