From: g...@turnstep.com
To: dbi-dev@perl.org
Subject: Re: Oracle ping
Date: Mon, 5 Nov 2012 02:47:06 +
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Also by the time an application does execute some SQL, the the
On 05/11/12 02:47, Greg Sabino Mullane wrote:
Also by the time an application does execute some SQL, the the
connection/node/server/network could have dropped and so the application
'will have to check recover from write failures at that point anyway.
This is a bit of a red herring. You
On 05/11/12 15:35, Charles Jardine wrote:
On 05/11/12 02:47, Greg Sabino Mullane wrote:
Also by the time an application does execute some SQL, the the
connection/node/server/network could have dropped and so the application
'will have to check recover from write failures at that point
I would tend to think that such a ping would be a special case, but I agree
with you to keep it as is:
Simply because overloading ping() with a complete eval'ed select statement
would be trivial. And the opposite isn't.
---
Henri Asseily
henri.tel
On Nov 5, 2012, at 4:35 PM, Charles Jardine
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
I rather strongly disagree. It is possible to do useful work over a
connection in situations when a 'simple select' is not possible.
My production Oracle database is protected by a physical standby database.
Ah, well in that case I
