Well, I'm using SQLObject, so I'm dependent on SQLObject's pooling (maybe this can be switched off, though, I didn't look). I'm really considering to switch to Postgresql now, which is possible thanks to the abstraction provided by SQLObject, but it still would be a major step. I'm wondering, if this could help, or if I'd just take my problems to another backend... ?!
A little while ago Luke Opperman posted (on the SQLObject list) a little recipe to use Webware's DBPool with SQLObject. Maybe you could use that together with the resilient DBPool. It would be nice to move that into SQLObject as well, since SQLObject pools would be pretty easy to make database-specific (which I think this pooling would have to be, since there's no DBAPI standard for pinging, which I think is necessary for this resilience). But I'd have to look more closely at this stuff to be sure what the appropriate implementation is on the SQLObject side.
-- Ian Bicking | [EMAIL PROTECTED] | http://blog.ianbicking.org
------------------------------------------------------- This SF.Net email sponsored by: ApacheCon 2003, 16-19 November in Las Vegas. Learn firsthand the latest developments in Apache, PHP, Perl, XML, Java, MySQL, WebDAV, and more! http://www.apachecon.com/ _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
