sybperl-l Archive

From: michael dot peppler at bnpparibas dot com
Subject: Re: DBD::Sybase 1.05_02 on CPAN
Date: Jul 8 2005 6:24AM

[sorry for top posting... bloody lotus notes...]

Running sp_procxmode only sets a flag in sysobjects (I think).
Unless your procs have some very specific code that would make them not
work in chained mode (and to be honest I don't know what that would be!),
then it should run with no problems.

Michael




Internet
matthew.persico@gmail.com@peppler.org - 08/07/2005 00:27


Please respond to matthew.persico@gmail.com

Sent by:    owner-sybperl-l@peppler.org

To:    mpeppler

cc:    sybperl-l


Subject:    Re: DBD::Sybase 1.05_02 on CPAN


On 7/7/05, Michael Peppler  wrote:
> On Thu, 2005-07-07 at 12:11 -0400, Matthew Persico wrote:

[snip]

> The change *should* be transparent. The only issue that you may see is
> if you are running stored procedures in AutoCommit OFF mode, and the
> procs haven't been set (enabled) for the chained mode (see
> sp_procxmode).
> In that case it's a simple matter of executing sp_procxmode to enable
> CHAINED mode for the procedures.

So even if I missed the condition in testing, the production code
would fail, we execut sp_procxmode on the proc and re-run the job.

Is it a bad thing to blanketly sp_procxmode all procs ahead of time?

> Alternatively, build DBD::Sybase with the chained mode default off.
> (still, the chained mode is how AutoCommit is handled with Sybase for
> ODBC and JDBC, so I guess it makes sense to use it here as well.)

Yeah, but since 99.9999% of our coding is Perl, I don't worry about
J/ODBC. I might just build with default off to save myself the hassle.

--
Matthew O. Persico




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.