Re: [Rails-core] automatic db retries

2005-12-09 Thread Rick Bradley
* Jeremy Kemper ([EMAIL PROTECTED]) [051209 15:50]: > http://dev.rubyonrails.org/ticket/3133 I owe you a beer, man. I was about 45 minutes from making that same patch. I somehow missed that ticket in the timeline. Thanks! Rick -- http://www.rickbradley.comMUPRN: 972

Re: [Rails-core] automatic db retries

2005-12-09 Thread Jeremy Kemper
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Dec 9, 2005, at 8:18 AM, Wilson Bilkovich wrote: Sorry to resurrect an old thread, but what about just defining a "no-op" query for each adapter. In Oracle, that would be, say, "select * from dual". Many Java connection pool implementations have

Re: [Rails-core] automatic db retries

2005-12-09 Thread Jeremy Kemper
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Dec 9, 2005, at 10:50 AM, Rick Bradley wrote: Not only that, but with 0.14.4 we've turned up a problem on Oracle with transaction isolation in tests. Basically, if we have a test that calls some AR functionality which happens to use a transac

Re: [Rails-core] automatic db retries

2005-12-09 Thread Rick Bradley
* Wilson Bilkovich ([EMAIL PROTECTED]) [051209 11:20]: > Sorry to resurrect an old thread, but what about just defining a > "no-op" query for each adapter. In Oracle, that would be, say, > "select * from dual". > Many Java connection pool implementations have such a thing, and > execute it when a

Re: [Rails-core] automatic db retries

2005-12-09 Thread Wilson Bilkovich
Sorry to resurrect an old thread, but what about just defining a "no-op" query for each adapter. In Oracle, that would be, say, "select * from dual". Many Java connection pool implementations have such a thing, and execute it when a connection is assigned. If it fails, the connection is closed a