jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bryan Davis <brda...@bea.com>
Subject Re: Database PersistenceManagers (was "Results of a JR Oracle test that we conducted)
Date Mon, 05 Mar 2007 18:28:25 GMT
Some drivers also use the compiled statement for  a PreparedStatement even
if a new instance of PreparedStatement is created each time.  This seems to
be the case for the driver's we are using, although I can't say that

On 3/3/07 7:11 AM, "Stefan Guggisberg" <stefan.guggisberg@gmail.com> wrote:

>> There is a persistence manager with an ASL license called
>> "DataSourcePersistenceManager" which seems to the PM of choice for people
>> using Magnolia (which is backed by Jackrabbit).  It also uses prepared
>> statements and eliminates the current single-connection issues associated
>> with all of the stock db PMs.  It doesn't seem to have been submitted back
>> to the Jackrabbit project.  If you Google for
>> "com.iorgagroup.jackrabbit.core.state.db.DataSourcePersistenceManager" you
>> should be able to find it.
> thanks for the hint. i am aware of this pm and i had a look at it a couple of
> months ago. the major issue was that it didn't implement the correct/required
> semantics. it used a new connection for every write operation which
> clearly violates the contract that the write operations should occur within
> a jdbc transaction bracket. further it creates a prepared stmt on every
> load, store etc. which is hardly efficient...

Notice:  This email message, together with any attachments, may contain
information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated
entities,  that may be confidential,  proprietary,  copyrighted  and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.

View raw message