PEPPLER.ORG
Michael Peppler
Sybase Consulting
Menu
Home
Sybase on Linux
Install Guide for Sybase on Linux
General Sybase Resources
General Perl Resources
Freeware
Sybperl
Sybase::Simple
DBD::Sybase
BCP Tool
Bug Tracker
Mailing List Archive
Downloads Directory
FAQs
Sybase on Linux FAQ
Sybperl FAQ
Personal
Michael Peppler's resume

sybperl-l Archive

Up    Prev    Next    

From: Michael Peppler <mpeppler at peppler dot org>
Subject: RE: Can transactions span databases?
Date: Nov 8 2001 11:10PM

Scott Zetlan writes:
 > > -----Original Message-----
 > > From: owner-SYBPERL-L@list.cren.net
 > > [mailto:owner-SYBPERL-L@list.cren.net]On Behalf Of Michael Peppler
 > > Sent: Thursday, November 08, 2001 5:08 PM
 > > To: SybPerl Discussion List
 > > Subject: Re: Can transactions span databases?
 > >
 > >
 > >  > 1) Is the scope of an explicit transaction the data server or
 > > the database?
 > >
 > > The data server (i.e. the *connection*).
 > >
 > 
 > Well, for the sake of precision, the scope of a transaction is probably
 > confined to a Sybase context, but that should be transparent to you unless
 > you start doing things like
 > $dbh1 = new Sybase::DBlib "user", $password;
 > $dbh2 = $dbh1->new "user2", $password2;

Heheheh... I wonder what the Sybase:: modules do in this case.

I suspect that they use the stringyfied value of $dbh1 as the package
name, and then allocate a new connection (which isn't quite right).

Michael
-- 
Michael Peppler - Data Migrations Inc. - http://www.mbay.net/~mpeppler
mpeppler@peppler.org - mpeppler@mbay.net
International Sybase User Group - http://www.isug.com