hi Bruce
Thanks for your quick reply. I am looking to do that because a couple of
reasons. One it is more efficient to have the OQL compiled once, prior to
program execution, esp if it is statically known. Second, my boss wants it,
for one so we can look at the generated OQL and possibly use it as the
basis for further optimization if necc, e.g. we have domain specific
knowledge.
Thanks
> This one time, at band camp, Srinivas Nedunuri said:
>
> SN>I am evaluating Casator and have been through the documentation to try
and
> SN>find an answer to this question but have not much luck.
> SN>
> SN>If the OQL is known ahead of time (at compile time) is there any way
to get
> SN>the tool to output the corresponding SQL? The idea is that I can then
run
> SN>the generated SQL against the generated DB schema at runtime
>
> Srinivas,
>
> I can certainly provide a method for doing this as it is quite simple.
But I'm
> curious to know why you want Castor to only produce SQL. Do you want to
> prevent Castor from executing that SQL against the database for some
reason?
>
> 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
>
--
www.inferdata.com
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev