Hi Lukas,

Thanks for the quick reponse and the valuable answers!
It would be really interesting to know more about the implementation of 
jooq-meta with the help of jdbc drivers metadata.
As i understood that can speed up the processes of setting up a new jooq 
dialect for our database right?

eager to know more...

best regards 

Marc.



Am Dienstag, 27. November 2012 17:33:53 UTC+1 schrieb Lukas Eder:
>
> Hi Marc, 
>
> > We (EXASOL), plan to develop a database integration for JOOQ. 
>
> Great news and thanks for your interest! 
>
> > What is required to appear on your list of planned integrations. 
>
> That's the easiest part. Done: 
> https://github.com/jOOQ/jOOQ/issues/1985 
>
> > Also it would be very interesting for us to know how much development 
> time 
> > would be required for such an integration for a database system similar 
> to 
> > oracle. 
>
> Unlike with other database abstraction frameworks, things are a bit 
> more tricky to integrate in jOOQ, depending on how far you want to go. 
> This is due to the fact that jOOQ takes into account subtle SQL 
> dialect differences for advanced SQL features and quite a few 
> functions. 
>
> There are several tasks with rough estimates: 
> - 2-3d for the first-time integration (i.e. understanding jOOQ's 
> integration tests and getting things to run) 
> - 1-2d for a "standard" jooq-meta integration (exotic data types, UDT 
> support, SP's may take a bit longer) 
> - 2-3d to fix integration tests (and the API documentation, with all 
> the @Support annotations) 
>
> > As i understood you have to implement an extension of AbstractDatabase 
> and 
> > related classes in jooq-meta and adjust required tests. 
>
> Yes, that's a rough summary. An option is also to skip the jooq-meta 
> part and implement this ticket here - if your JDBC driver's 
> DatabaseMetaData can deliver the required meta information: 
> https://github.com/jOOQ/jOOQ/issues/1636 
>
> > Is there any Evaluation process for contributed db integrations? 
>
> My requirements are: 
>
> - I have to be able to easily run and execute the integration tests on 
> a free developer licensed database instance (this includes the JDBC 
> driver) 
> - I need access to extensive SQL documentation. Free 1st level support 
> is a plus, too. 
> - If that instance doesn't further cripple my poor laptop (hello 
> Oracle, DB2, and 12 other DBs!) that's a plus, too :-) 
>
> Then, there are maintenance considerations. Adding new features (e.g. 
> new function support, new SQL feature support) becomes more and more 
> complex, as the number of supported databases grows. Do you see your 
> potential contribution as a long-term affiliation with jOOQ, or as a 
> one-time contribution? 
>
> I'm also open to more formal affiliations, such as the one recently 
> offered by CUBRID: 
>
> http://www.cubrid.org/blog/cubrid-life/first-batch-of-donations-to-opensource-projects-from-cubrid-affiliates-program/
>  
>
> It included a one-time donation, as well as free promotion for jOOQ on 
> the CUBRID blog and website. Should you be interested, feel free to 
> contact me through a P.M. 
>
> N.B: it would probably be interesting to see your database on this page: 
>
> http://en.wikipedia.org/wiki/Comparison_of_relational_database_management_systems
>  
>
> Best Regards, 
> Lukas 
>

Reply via email to