Definitely OJB supports PreparedStatements, it has for a while now. What I wanted to
do was pool/cache the OQL Queries to avoid the OQL->OJB PB Compiled format->SQL steps.
I have implemented this for another OR mapper (Castor), and under high concurrency it
made a nice difference. I have been very busy lately and haven't had time to do much
on OJB. That should change soon.
Cheers,
Matthew
-----Original Message-----
From: Phil Warrick [mailto:[EMAIL PROTECTED]]
Sent: Tue 1/28/2003 7:15 AM
To: OJB Users List
Cc:
Subject: Prepared statement support
Hi,
Back some time ago, Matthew Baird mentioned looking into explicit
prepared statement querying for better OQL support and possibly better
performance (reduced query parsing, reduced network traffic, etc.).
http://archives.apache.org/eyebrowse/ReadMsg?[EMAIL PROTECTED]&msgId=428068
Was there any conclusion reached? I have seen significant performance
improvements in other O/R mappers (having ODMG support) that I have used
that supported this. You probably don't need much convincing as you've
decided to use (implicit) prepared statements internally.
An example of the convergence of better performance AND better standards
compliance? :)
Thanks,
Phil
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
<<winmail.dat>>
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
