What problem is that? I don't think there's much you can do beyond
re-connecting, which Apache::DBI does.
Well, the thing about SQLRelay is that it pools database connections,
which is good when you want to have plenty of persistent connections to
different databases.
My only problem with
List,
I came across http://www.firstworks.com/sqlrelay.html the other day.
Have any of you come across this product before. With the whole problem
of providing seemless recovery at the client side from database
failure this tool seems quite productive. I've not used it but figured
maybe
Richard Clarke wrote:
I came across http://www.firstworks.com/sqlrelay.html the other day.
Have any of you come across this product before.
It's been discussed here before (see the archives) but no one has talked
about any real experience with it yet. Try it out and tell us what you
Perrin Harkins wrote:
Richard Clarke wrote:
I came across http://www.firstworks.com/sqlrelay.html the other
day. Have any of you come across this product before.
It's been discussed here before (see the archives) but no one has
talked about any real experience with it yet. Try it
to automatically retry on
another database if it fails. For that, you would need to add some
extra code to catch the exception, recognize it as a connection failure,
make a new connection, and retry the query. I don't see anything on the
SQL-Relay pages about this sort of ability.
- Perrin
