I checked the Bug database on peppler.org and it turns out this one is
documented. I am linking the workaround just in case someone else has
the same issue:

http://www.peppler.org/bugdb/view?bug_id=633

Regards
Gurunandan


On Wed, 2008-08-27 at 21:47 +0530, Gurunandan R. Bhat wrote:

> Friends,
> 
>     I am building an application with CAP::DBH and DBD::Sybase. 
> 
>     Unfortunately DBD::Sybase implements ping()  that causes it to fail
> if there is an active statement handle. I have tested this in a
> stand-alone script without CGI or CA. DBD::Sybase::ping() works after I
> have called finish() on all statement handles and fails otherwise.
> 
>     Since CAP::DBH implements lazy loading via a ping test to check an
> existing connection handle before creating one, my app crashes. 
> 
>     How can I work around this (broken? ping()) in DBD::Sybase.
> 
> I Really appreciate your help
> 
> Regards
> Gurunandan
> 
> 
> #####  CGI::Application community mailing list  ################
> ##                                                            ##
> ##  To unsubscribe, or change your message delivery options,  ##
> ##  visit:  http://www.erlbaum.net/mailman/listinfo/cgiapp    ##
> ##                                                            ##
> ##  Web archive:   http://www.erlbaum.net/pipermail/cgiapp/   ##
> ##  Wiki:          http://cgiapp.erlbaum.net/                 ##
> ##                                                            ##
> ################################################################
> 

#####  CGI::Application community mailing list  ################
##                                                            ##
##  To unsubscribe, or change your message delivery options,  ##
##  visit:  http://www.erlbaum.net/mailman/listinfo/cgiapp    ##
##                                                            ##
##  Web archive:   http://www.erlbaum.net/pipermail/cgiapp/   ##
##  Wiki:          http://cgiapp.erlbaum.net/                 ##
##                                                            ##
################################################################

Reply via email to