Hi Jon,

we are thinking about a refactoring of the OQL parser and SQL generation for quite some time. At the moment we plan to work on that for next feature release 1.1. The targets of the refactoring are not yet defined finally but main points are:

- use ANTLR to generate OQL parser instead of hand written code
- make OQL parser and SQL generation plugable
- offer similar possibilities as with current OQL syntax
- fix some bugs if possible

How we go about extentensions of the syntax is not defined yet. The problem here is that our current syntax is a custom one not compatible to any standard. It has mainly been influenced by ODMG 3.0 OQL definition but also not complies to that. As we like to develope Castor to get complient with JPA(EJB3.0) in the future we may decide to not further extend current OQL syntax but instead implement EJBQL complient parser with extended functions.

Our targets in most cases do not depend on what we like to do but on the demands of our users. How fast we progress with tasks does not only depend on our targets but also on how much support/help we get from the users ;-)

Having said that we expect syntax extensions to be much easier when generating OQL parser by ANTLR as it is with our current codebase. In addition it may be interesting for you to know that I frequently use passthrough SQL queries as I also miss some syntax elements at OQL.

Regards
Ralf


Jon Wilmoth schrieb:
I have two questions:
1) Looking at http://www.castor.org/oql.html#Status, it says phase 3 is where the project is at. Is there a target for phase 4 or phase 5? 2) Is "unique collectionExpr" also part of OQL phase 4? Thanks,
Jon

-------------------------------------------------
If you wish to unsubscribe from this list, please send an empty message to the following address:

[EMAIL PROTECTED]
-------------------------------------------------


-------------------------------------------------
If you wish to unsubscribe from this list, please send an empty message to the following address:

[EMAIL PROTECTED]
-------------------------------------------------

Reply via email to