You could actually try to use the future Postgres schema for code generation and run jOOQ queries with Postgres-generated classes against your MySQL database. In principle, this could work, even if using several database types is not yet fully supported by jOOQ (it will be in 1.6.1 or 1.6.2).
In any case, as far as I remember MySQL 4.0, there wasn't even support for foreign key relationships, so maybe you'll run into other problems later on... 2011/6/7 Maxim Usenko <[email protected]>: > It's a billing, old and very ... agh. > > I wrote some wrappers around its database. Now i want to rewrite my > ugly code and jooq is what i need. In 2 or 3 months we will upgrade it > and postgresql is what i whant in future. > What can i do now to generate classes? > > thanks for helping > > On 7 июн, 16:24, Maxim Usenko <[email protected]> wrote: >> I'm using mysql 4.0.20. Maybe in this my problem? There is no >> INFORMATION_SCHEMA and, how i understand, it's was added in mysql >> 5.0+ ?! >> >> I hope you understand me and my english (i'm reader, not writer) =) >> >> On 7 июн, 16:08, Lukas Eder <[email protected]> wrote: >> >> >> >> >> >> >> >> > When you use these connection properties in a standalone application: >> >> > #Configure the database connection here >> > jdbc.Driver=com.mysql.jdbc.Driver >> > jdbc.URL=jdbc:mysql://192.168.4.10/ >> > jdbc.Schema=db_name >> > jdbc.User=db_user >> > jdbc.Password=db_password >> >> > will you then have access to the INFORMATION_SCHEMA tables? >> > Also, have you tried using >> >> > jdbc.URL=jdbc:mysql://192.168.4.10/[db_name] >> >> > I'm not sure, jOOQ will work correctly if no database is specified in >> > the connection URL
