Hi Charles, from 0.9.7 to 0.9.9 nothing changed at the OQL syntax but we had to change the generation of the SQL statements according to the introduction of polymorphism. Especially the generated SQL for classes that take part in an extend declaration of the mapping have changed significantly. Even if this should be hidden from castor users it will hit you when you use CALL SQL ... AS ... statements.
Having said that it may be possible that you recognized a bug where we generate wrong SQL in a usecase not covered by or test framework at the moment. I am quite interested to get more information about that problem, like full stacktrace, mapping, failing sql statement. Much better then only informations would be a testcase to reproduce the problem ourself ;-) Regards Ralf Charles Read schrieb: > I substituted castor-0.9.9.jar for castor-0.9.7.jar, > rebuilt my webapp and then redeployed it. > > Mostly, everything worked ok. However, at some > point I got a PersistenceException (that in turn was > triggered by an SQLException). The exception message > says that "You have an error in your SQL syntax; ..." > > I am using MySQL 4.1. The webapp works fine > with castor-0.9.7.jar. > > Question: has OQL changed in castor-0.9.9.jar? > > NOTE: I looked at the docs for OQL on castor.org, > but found no reference to OQL changes for 0.9.9. > > Thanks. > > ------------------------------------------------------------------------ > Yahoo! for Good > Click here to donate <http://store.yahoo.com/redcross-donate3/> to the > Hurricane Katrina relief effort. -- Syscon Ingenieurbüro für Meß- und Datentechnik GmbH Ralf Joachim Raiffeisenstraße 11 D-72127 Kusterdingen Germany Tel. +49 7071 3690 52 Mobil: +49 173 9630135 Fax +49 7071 3690 98 Email: [EMAIL PROTECTED] Web: www.syscon-world.de ------------------------------------------------- If you wish to unsubscribe from this list, please send an empty message to the following address: [EMAIL PROTECTED] -------------------------------------------------
