Re: OJB not robust against database or network failures

[Thomas Mahler]

Hi all,

<snip>

I'm not an expert either! But perhaps a hard coded default query from
Platform which can be overridden by the user by a validationQuery
attribute in jdbc-connection-descriptor or connection-pool?

Thanks, attribute in connection-pool seems to be a good solution,
because
we only need this feature when using pooled connectins. If not set we
only
do a isClosed() validation.

I think we should also provide a default validationQuery. I suggest to use a simple "SELECT COUNT(*) FROM OJB_SEQ", as the ojb sequencemanager table will be used in about 95% of all OJB scenarios.

This an urgently needed feature!

cheers,
Thomas



--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>