Hi again Jaideep, Ganguli Jaideep wrote:
Thanks Thomas
If I implement my own SqlGenerator plug in would it then be used for all
my domain objects?
OR
(This is more likely what i'm looking for)
Is it possible for me to localize the SQL optimizations for a particular domain object (with which the data access has been identified as a
bottleneck). For the others I would want to just let the default OJB
SQlGenerator handle sql generation.
It would be used *for all* domain classes. But you could derive your new Generator from the existing one. This way you just need an if-statement to detect which SQL should be generated...
cheers,
Thomas
Thanks again.Jaideep Mahler Thomas wrote:Yes! You can implement your own SqlGenerator an plug it into the OJB PersistenceBroker. There have been users doing this for STored procedures! cheers, Thomas-----Urspr�ngliche Nachricht----- Von: Ganguli Jaideep [mailto:[EMAIL PROTECTED]] Gesendet: Dienstag, 14. Januar 2003 16:43 An: OJB Users List Betreff: SQL Optimization/Stored Procedure Hi, Is there some way of making the Persistence Broker API (or JDO or ODMG) call an optimized SQL (or stored procedure) instead of using the default SQL it will use? Thanks Jaideep -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
