I'm curious how feasible it would be to write a Java-based evaluator of
Hibernate queries, or at least leverage the existing parser code to gain
access to the abstract syntax tree. 

One possibility is that certain subsets of queries (most filters, I
think) could be run within the JVM, saving a db query.

Also, a translator could allow Hibernate query language to be used with
other persistence engines (ok, this is not so compelling since Hibernate
is the best :)

But really, the query language seems very clean and simple, and I
believe has the potential to be useful in scenarios even outside of
persistence. Kind of like JXPath, but more SQL-like. This way all the
queries in my application could use the same language, regardless of
whether there is an underlying database.

I've looked at the cirrus.hibernate.query package and most of it is
pretty generic, but there are some obvious places where the persistence
stuff creeps in. Is it worth persuing reusing this code? If not, do you
anticipate many changes to the query language going forward?

Thanks,
Chris





-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
hibernate-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/hibernate-devel

Reply via email to