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: "Orton, Yves" <yves dot orton at de dot mci dot com>
Subject: About prepared statements asnd transactions....
Date: Oct 11 2005 10:10AM

Hi All,

Im wondering what people think about having the option to have client side
statement handles that arent translated to server side temporary stored
procs.

This idea came to mind when I was using a large number of prepared queries
and discovered that doing so can silently lead to inadverdant transactional
violations. 

I was thinking basically that in some cases the advantage of stored procs is
the simplicity of use and not the fact that the query is being created as a
temporary stored proc on the server that can be called via RPC. If it were
possible to have statement handles that were client side and just
responsible for appropriately quoting their placeholders then there would be
no issues with transasctional problems and stored proc creation or whatever.


IIUIC this would allow using multiple statement handles in transasctions,
and if triggered by the presence of AutoCommit would make it much more
difficult to transasctionally blow your foot off.

Maybe this mail reveals a serious flaw in understanding of how DBD::Sybase
works, if so please straighten me out.

Cheers,
Yves