This one time, at band camp, Srinivas Nedunuri said:
SN>Thanks for your quick reply. I am looking to do that because a couple of
SN>reasons. One it is more efficient to have the OQL compiled once, prior to
SN>program execution, esp if it is statically known. Second, my boss wants it,
SN>for one so we can look at the generated OQL and possibly use it as the
SN>basis for further optimization if necc, e.g. we have domain specific
SN>knowledge.
Srinivas,
OK, now I understand what it is for which you are searching. The
SQL for creating, reading, updating and deleting is generated by
the SQLEngine via the metadata in the mapping descriptor upon
initializing Castor. All other SQL is either generated by the Castor
OQL engine at runtime or the actual SQL is provided by the user via
the CALL SQL keywords to the Database.getOQLQuery() method.
If you need more or different info than this please let me know.
Bruce
--
perl -e 'print unpack("u30","<0G)[EMAIL PROTECTED]&5R\"F9E<G)E=\$\!F<FEI+F-O;0\`\`");'
The Castor Project
http://www.castor.org/
Apache Geronimo
http://incubator.apache.org/projects/geronimo.html
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
