---------------------------------------- > From: g...@turnstep.com > To: dbi-dev@perl.org > Subject: Re: Oracle ping > Date: Mon, 5 Nov 2012 02:47:06 +0000 > > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: RIPEMD160 > > >> 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 could say that about any database action, > anytime ever. I personally think a simple select is better than relying > on a low-level library call, as it does a more complete end-to-end check > that is almost certainly closer to what the caller is going to use the > connection for. >
Yes I am comming over to that way of thinking. Might just need some clarification in the DBD::Oracle doc then. i.e. May be able to ping but you cannot run querries or alike >> Mysql has 'mysql_ping' the same sort of thing as OCIPing except it can >> reconnect. > > Does it automatically reconnect? That certainly seems like the wrong thing > to do, especially in light of the docs for connect_cached. got that from the MySql doc it can be set up to reconnect if ping fails http://dev.mysql.com/doc/connector-python/en/myconnpy_MySQLConnection_ping.html> not didn't check the DBD driver to see if it does this though. Perhaps just some clarification on the DBI spec would be better to get all the DBD that impliment it in line and doing the same thing?? Cheers > - -- > Greg Sabino Mullane g...@turnstep.com > End Point Corporation http://www.endpoint.com/ > PGP Key: 0x14964AC8 201211042146 > http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 > > -----BEGIN PGP SIGNATURE----- > > iEYEAREDAAYFAlCXKI0ACgkQvJuQZxSWSsgMAACg4VdWNpWYgyrENkXKhO9G5Mez > /fkAoM6hBowTxDCAvKOD6G7yQBgItiO1 > =85sU > -----END PGP SIGNATURE----- > >
