Well JOOQ certainly influnced the query DSL API which we use. JOOQ is certainly very mature and can express much more complex SQL statements.
JOOQs API is more database centric and I was looking for a framework with a similar query DSL but which produced more Pojo like objects.
One of the most interesting things about BarleyDB is that it can be used (if so desired) without any compilation. You can import a schema from an XML file and the use the meta model to query and to save data.
BarleyDB also provides:
optimistic locking,
query batching,
access-control checks - via plugin,
auditing - via plugin,
insert / update statement reordering for increased batch sizes.
Yes, I agree with you about relational data, BarleyDB holds the relational data in memory and then provides Pojo proxies to it. Combining an active record approach with a domain model Pojo approach if you like.
This is why it is fully possible to use BarleyDB without compiling any classes, you can just use the in memory model instead.
JOOQs API is more database centric and I was looking for a framework with a similar query DSL but which produced more Pojo like objects.
One of the most interesting things about BarleyDB is that it can be used (if so desired) without any compilation. You can import a schema from an XML file and the use the meta model to query and to save data.
BarleyDB also provides: optimistic locking, query batching, access-control checks - via plugin, auditing - via plugin, insert / update statement reordering for increased batch sizes.
Scott