Hi all. Simple question.
Is it advisable to use local to temporarily modify parts of a DBD::MySQL db handle for the 1 place in a big program where i want to use a transaction, or is this not going to work like i think?
What im trying to accomplish is the localized change of the $dbh attributes to do the transaction, then commit it. So as i see it, when i exit the enclosing block, the localized values will go out of scope and the originals will be restored. In reality, the enclosing block will be a function, but i wanted as simple an example as possible.my $dbh = ...; ... { # enclosing block for transaction # local $dbh->{'AutoCommit'} = 1; # UPDATE - thanks Corion local $dbh->{'AutoCommit'} = 0; local $dbh->{'PrintError'} = 0; # do the transaction queries ... $dbh->commit(); }
I already wrote a little test script that seems to work properly, but i am new to transactions, and dont use local that much, and am looking for any possible problems that this may cause.
I am mostly using whats in the MySQL cookbook section 15.4 Using Transactions in Perl Programs, but they dont use local, and using local seems cleaner to me.
In reply to local & DBD::mysql by shemp
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |