FreeTDS Development Group

[Ravi Krishna <rkusenet AT hotmail.com>]

Thanks for the reply. My comments in-line
 

> I never bumped into the limitations you describe because my DBI
> programs never have more than one statement handle per connection. 
 
Hmm. How do you handle situation when you have to talk to two different
servers, one in prod and one in dev. You do need two separate db handles
and the moment you do that, perl dbi/freetds disallows auto commit to be
turned off. A serious limitation IMO.

> Your question implies you'd like to have a set of statement handles,
> on the same connection, all prepared, and be able to execute them under
> transaction control. 

Correct. I do perl coding with other RDBMS too like Oracle and db2 and I like 
to
prepare all statements I need right at the beginning and then use more than 
one
statement handles, each doing inserts to different table, in a serialized way.
 
You are right. Eventually I worked it around by passing all values to a sproc 
and
encapsulated the logic within sproc of inserting to different tables with 
BEGIN TRAN COMMIT TRAN.