Michael Peppler
Sybase Consulting
Sybase on Linux
Install Guide for Sybase on Linux
General Sybase Resources
General Perl Resources
BCP Tool
Bug Tracker
Mailing List Archive
Downloads Directory
Sybase on Linux FAQ
Sybperl FAQ
Michael Peppler's resume

sybperl-l Archive

Up    Prev    Next    

From: michael dot peppler at bnpparibas dot com
Subject: Re: About prepared statements asnd transactions....
Date: Oct 13 2005 5:58AM

I believe DBD::ODBC has similar problems, in particular when used against

That being said - if this behavior is really needed then I'd be grateful
for a patch.


Internet - 12/10/2005 20:58

Sent by:

To:    sybperl-l


Subject:    Re: About prepared statements asnd transactions....

Ed Avis wrote:
> I appreciate that to some extent we have to follow the existing
> behaviour and not break compatibility - but don't add any more magic
> workarounds unless they're something the programmer must be aware of
> and deliberately ask for.

Whether it's officially part of the DBI API or not, DBI programmers have
to expect to be able to have multiple active sth's. DBD:Sybase is the only
DBD of any relevance that doesn't support this, and it's a barrier to
major database applications such as Bugzilla to Sybase. Not supporting this
capability is seen by some as a serious deficiency. There are at least two
precendents of other DBDs emulating this behavior, so it's hardly uncommon.
The DBI is all about having a consistent interface to the database, and I'm
sure there are already plenty of "magic workarounds" in DBD::Sybase to make
it work the way DBDs are expected to work. I'm not advocating adding a new
magic workaround, but rather *fixing* the current workaround which doesn't
allow for multiple active sth's inside of a transaction. Make it an option
you must, but this capability is sorely needed in DBD::Sybase.

This message and any attachments (the "message") is
intended solely for the addressees and is confidential. 
If you receive this message in error, please delete it and 
immediately notify the sender. Any use not in accord with 
its purpose, any dissemination or disclosure, either whole 
or partial, is prohibited except formal approval. The internet
can not guarantee the integrity of this message. 
BNP PARIBAS (and its subsidiaries) shall (will) not 
therefore be liable for the message if modified. 


Ce message et toutes les pieces jointes (ci-apres le 
"message") sont etablis a l'intention exclusive de ses 
destinataires et sont confidentiels. Si vous recevez ce 
message par erreur, merci de le detruire et d'en avertir 
immediatement l'expediteur. Toute utilisation de ce 
message non conforme a sa destination, toute diffusion 
ou toute publication, totale ou partielle, est interdite, sauf 
autorisation expresse. L'internet ne permettant pas 
d'assurer l'integrite de ce message, BNP PARIBAS (et ses
filiales) decline(nt) toute responsabilite au titre de ce 
message, dans l'hypothese ou il aurait ete modifie.