Skip Menu |

This queue is for tickets about the DBD-SQLAnywhere CPAN distribution.

Report information
The Basics
Id: 104410
Status: resolved
Priority: 0/
Queue: DBD-SQLAnywhere
People
Owner: smirnios [...] sybase.com
Requestors: davidp [...] preshweb.co.uk
Cc:
AdminCc:
Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: 2.13

History Show all quoted text
  Wed May 13 14:32:57 2015 davidp [...] preshweb.co.uk - Ticket created
Subject: ping method throws exception if no connection
A user of my Dancer::Plugin::Database raised an issue experiencing problems when using DBD::SQLAnywhere - D::P::D uses the ping method to check that the database connection is still alive, but the simple implementation in DBD::SQLAnywhere will result in an exception if the connection is dead. As the ping method is one expressly designed to be called to find out whether the connection is alive, I feel it should catch the exception itself, and simply return 1 or 0 to indicate whether the connection is usable or not - what do you think? I don't mind working round it in D::P::D if required, but I think the better place to fix it is within DBD::SQLAnywhere so it fixes it for all users of this database driver. The issue raised for D::P::D is at: https://github.com/bigpresh/Dancer-Plugin-Database/issues/65
  Thu May 14 13:54:35 2015 smirnios [...] sybase.com - Correspondence added
On Wed May 13 14:32:57 2015, BIGPRESH wrote: Show quoted text
> A user of my Dancer::Plugin::Database raised an issue experiencing > problems when using DBD::SQLAnywhere - D::P::D uses the ping method to > check that the database connection is still alive, but the simple > implementation in DBD::SQLAnywhere will result in an exception if the > connection is dead. > > As the ping method is one expressly designed to be called to find out > whether the connection is alive, I feel it should catch the exception > itself, and simply return 1 or 0 to indicate whether the connection is > usable or not - what do you think? > > I don't mind working round it in D::P::D if required, but I think the > better place to fix it is within DBD::SQLAnywhere so it fixes it for > all users of this database driver. > > The issue raised for D::P::D is at: > https://github.com/bigpresh/Dancer-Plugin-Database/issues/65
Fixed in version 2.13.
  Thu May 14 13:54:35 2015 The RT System itself - Status changed from 'new' to 'open'
  Thu May 14 13:54:36 2015 smirnios [...] sybase.com - Status changed from 'open' to 'resolved'
  Thu May 14 13:54:37 2015 smirnios [...] sybase.com - Taken
  Fri May 15 09:55:15 2015 smirnios [...] sybase.com - Fixed in 2.13 added