LIQUidFORM vs jOOQ

[Lukas Eder]

I hope my message gets read among all the spam you're getting in your
mailing list :)

I have found your tool on Google, and it looks like a quite promising.
Especially the experience you have concerning integration with JPA may
be useful to jOOQ, which stands for Java Object Oriented Querying.
jOOQ ships with a DSL similar to yours as a side-effect to the main
goals, which are:

- Soure code generation
- Full support for standard SQL, including UNIONs, nested SELECTs,
aliasing, all sorts of JOINs
- Large support for non-standard SQL, including UDTs, stored
procedures and other features

Is LIQUidFORM still active? Would you see any possible cooperation in
the field of JPA integration.

Check out https://sourceforge.net/apps/trac/jooq/wiki/Examples for
more information about jOOQ

[Eric Bottard]

Hello Lukas,

thanks for your interest in LIQUidFORM.

To answer your questions quickly : yes LF is still active, but not that much now that JPA 2 has come out with its typesafe criteria API. Not that LF and that API cover the exact same need, but I guess users would be more inclined to use that nowadays. This means that we're not adding new features to LIQUidFORM, only fixing outstanding bugs that prevent users to use the product correctly.

Unfortunately, I personally don't have any free time to dedicate to medium to large scale projects, but feel free to build on top of LIQUidFORM if you wish. Don't hesitate to ask questions either, as we'd be glad to answer them !

And congrats for your jOOQ library, as I know working on such projects is not an easy task.

eb.

--
You received this message because you are subscribed to the Google Groups "LIQUidFORM Users Mailing List" group.
To post to this group, send email to liquidfo...@googlegroups.com.
To unsubscribe from this group, send email to liquidform-use...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/liquidform-users?hl=en.

[Lukas Eder]

Hello Eric,

Thanks for your response. I can see from the activities of many similar projects like yours, that JPA2 seems to have brought many developers to the conclusion to go with the "standard", rather than rolling their own solutions or building upon great little libraries like yours. I personally think this is a pity, as the criteria API is not one of the most successful implementations for a JSR. One year after its introduction, I can't see much of that expected momentum, even if they copied from Hibernate.

That is one of my major sources of motivation for my own library, because I think many developers today, either developing against huge legacy databases, or on mobile devices, do not have a choice but staying close to SQL, either for the slimness of their codebase, or for the support of native, vendor-specific SQL features.

Anyway, in case building on top of JPA is an option in the near future, I'll happily re-consider LIQUidFORM again.

Thanks
Lukas

2010/12/26 Eric Bottard <eric.b...@gmail.com>