Martin Holz wrote:
Right. It's known that this is slow and (as you say) broken anyway. It's there as a quick hack that makes it work reasonably reliably in practice. Someone who actually knows how to use JDBC effectively really needs to look at this (though probably dumping the existing JDBC stores and adapting the proposed ones that were sent to this list a while ago (they're much more efficient, but last time I looked didn't actually work right in a few cases) - once fixed up, they'd be much better."Sven Steiniger" <[EMAIL PROTECTED]> writes:The optimization on JDBCDescriptorsStore is also simple and relates to the isConnect()-method. I have read a lot of discussions on this topic but maybe it's worth to start this thread again. This method causes a major slowdown because of executing a statement for every simple operation. I understand that it is necessary to ensure the 100% data integrity, but in normal environment it's very unlikely that the database connection is lost. Thus in general it should be safe enough to check the connection about every minute. So why not introducing an option in the domain-config where the connection-checking can be configured? Thus every project can choose the appropriate settings.
J2EEStore uses a much isConnected method. At FCH we use a
subclass of JDBCDescriptorStore, which overides the isConnected
with J2EEStore's implementation. We found the original store
to slow to be usable.
Mike
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
