Re: How to remove the warning: "there is already a transaction in progress" when using lock table

hello angeloulivieri,

i think you'll get answer from monks with great psql experience, but reading here and there i can guess it is not a Perl issue but a warning (yes just an annoying one) caused (if i understand correctly) by the driver: the transaction is already started and psql give back this warning (for you safety)

There are no rules, there are no thumbs..
Reinvent the wheel, then learn The Wheel; may be one day you reinvent one of THE WHEELS.

Comment on Re: How to remove the warning: "there is already a transaction in progress" when using lock table Download Code

Replies are listed 'Best First'.
Re^2: How to remove the warning: "there is already a transaction in progress" when using lock table by cavac (Prior) on Apr 14, 2016 at 06:11 UTC
Correct. With AutoCommit off, DBI/DBD::Pg automatically sends START TRANSACTION (or the identical BEGIN) when you do() or execute(). If you want explicit control over this, settings AutoCommit to true should work. See http://search.cpan.org/~timb/DBI-1.634/DBI.pm#AutoCommit and http://search.cpan.org/~turnstep/DBD-Pg-3.5.3/Pg.pm#AutoCommit_(boolean). "For me, programming in Perl is like my cooking. The result may not always taste nice, but it's quick, painless and it get's food on the table."	[reply]

Replies are listed 'Best First'.

Re^2: How to remove the warning: "there is already a transaction in progress" when using lock table
by cavac (Prior) on Apr 14, 2016 at 06:11 UTC

Correct. With AutoCommit off, DBI/DBD::Pg automatically sends START TRANSACTION (or the identical BEGIN) when you do() or execute().

If you want explicit control over this, settings AutoCommit to true should work.

See http://search.cpan.org/~timb/DBI-1.634/DBI.pm#AutoCommit and http://search.cpan.org/~turnstep/DBD-Pg-3.5.3/Pg.pm#AutoCommit_(boolean).

"For me, programming in Perl is like my cooking. The result may not always taste nice, but it's quick, painless and it get's food on the table."

[reply]