Is it reasonable to ask that JOOQ *createTableIfNotExists()* knows which
underlying SQL implementations that supports it natively and does a "SELECT
1 FROM ..." automatically for those that don't ??
JOOQ is supposed to hide such differences, but I think there is quite a lot
more to do to get there.
There are other similar issues, such as knowing which SQL types are
supported, if schemas are supported and probably a lot more I have not come
across yet. Perhaps a first step is to have a
* public class SQL { : :*
* public static boolean supports( SQLDialect dialect, Feature
feature ) { ... }*
* : : }*
*if( DSL.supports( dialect, Features.createTableIfNotExists() ) {}if(
DSL.supports( dialect, Features.dataType( Types.TIMESTAMP_WITH_TIMEZONE) )*
And many more...
I can see that JOOQ internals are dotted with similar checks here and
there, for instance to get the SQL rendering right.
WDYT?
Cheers
--
Niclas Hedhman, Software Developer
http://polygene.apache.org - New Energy for Java
--
You received this message because you are subscribed to the Google Groups "jOOQ
User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
