"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. How would the isConnected() method help for data integrity. The connection could still get lost between a call to isConnected and the next database statement. In which case the database would rollback the connection, so data integrity should be ensured. The database teststatement "select 1 from objects where uri is null" may be not as cheap as it looks. I got the impression, that postgres 7.2 does a complete sequencial scan on the 'objects' table. Looks like the query optimizer is not fool proof. Martin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
