Hello Philippe, Thanks for considering jOOQ. As you mentioned, jOOQ currently supports Sybase SQL Anywhere 12 as documented on the home page. There had currently not been any plans to also support Sybase Adaptive Server Enterprise as there had not been any need by jOOQ users, so far. The SQL Anywhere support was contributed by Espen Stromsnes who also has professional experience with Sybase. I will put support for Sybase ASE on the roadmap: https://sourceforge.net/apps/trac/jooq/ticket/800
If you wish to implement Sybase ASE support early, these are the steps you may want to consider: https://sourceforge.net/apps/trac/jooq/wiki/Contribute#Hints You can get some inspiration from the org.jooq.util.sqlite.SQLiteDatabase implementation. SQLite does not have any dictionary tables either (or "standard" tables as you called them). Instead, it provides a stored function returning a result set holding table/column/key information. That sounds similar to your "sp_help" procedure. As with SQLite, the most important data you should gather is about tables and primary keys. Once you have that, you can already get started with jOOQ. The second thing to do is to adapt dialect integration in jOOQ's core classes. I'm not sure if Sybase ASE and Sybase SQL Anywhere have the same SQL dialect. Usually, a new dialect needs an average of around 10 dialect "tweaks", when advanced SQL is involved (nested selects, limits, etc). I can further assist you, when you get this far. If you provide me with some information how to set up a free developer's license of Sybase ASE, I can also increase the priority of officially supporting Sybase ASE in jOOQ, and take your contribution into consideration. Cheers Lukas 2011/8/22 psevestre <[email protected]>: > Hi, > > I'm currently evaluating jOOQ for a number of projects for the > organization I consultt for but it seems that its support for Sybase > actualy aplies to Sybase Anywhere. Are there any plans to support > Sybase ASE in the horizon ? > > From what I could see in the source code, the generator expects to > find schema information in some "standard" tables, but ASE does not > support those tables. Instead, one usually uses the system proc > "sp_help" in order to gather schema information. > > In such scenario, which steps should I follow in order to support a > new database dialect ? > > > Regards, > > Philippe
