Hi Thomas,
Thanks a lot for adding a link!
I am acquainted with JaQu and I can see the similarities, especially
as far as the DSL is concerned.
JaQu seems to have a better approach to connecting query elements
within its DSL. As I can see there is less Java-induced "syntactic
overhead" because operations are not done on physical objects, such as
fields, but on "invisible" DSL-support classes or interfaces.
Particularly interesting is the idea to use anonymous objects and to
disassemble Java code ("natural syntax") in order to control JaQu
query behaviour. How well has this design been adopted by your users?
Are you going to further develop the "natural syntax" for complex
query conditions of any type?
jOOQ's DSL is only a side-effect of the fundamental idea jOOQ tries to
follow: close coupling of a database-interfacing framework (I
explicitly omit the term 'OR-mapper') with its underlying databases,
providing all SQL language features, as well as non-standard SQL
features such as UDTs, stored procedures etc. Integration with JPA/
EJB3 is on the roadmap but not a major priority.
Regards,
Lukas
On 13 Dez., 20:29, Thomas Mueller <[email protected]>
wrote:
> Hi,
>
> Thanks! I will add a link to your project. It's a bit different than
> JaQu -http://h2database.com/html/jaqu.html- I guess a bit more like
> JPA2.
>
> Regards,
> Thomas
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/h2-database?hl=en.
