Should we do both, a validationQuery attribute in connection-pool tag and a platform dependent (system table) query (Priority: attribute > platform)? Or only the platform dependent validationQuery? What should we do when PlatformDefaultImpl was used?
Armin ----- Original Message ----- From: "Matthew Baird" <[EMAIL PROTECTED]> To: "OJB Users List" <[EMAIL PROTECTED]> Sent: Wednesday, December 04, 2002 9:55 PM Subject: RE: OJB not robust against database or network failures Maybe we could make it a platform issue so that we can query system tables instead of app tables. I don't like to *have* to install that table as I don't use any sequences. -----Original Message----- From: Thomas Mahler [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 04, 2002 12:01 PM To: OJB Users List Subject: Re: OJB not robust against database or network failures 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]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
