Owen Hartnett wrote:
> At 10:14 AM -0400 8/28/07, Owen Hartnett wrote:
>> At 7:05 PM -0400 8/27/07, Tom Lane wrote:
>>> Owen Hartnett <owen@clipboardinc.com> writes:
>>>> I assign the transaction object to each of the commands, but it seems
>>>> that some tables will get updated, even when I call rollback. Is
>>>> something I'm calling secretly calling "commit" somewhere?
>>>
>>> Dunno anything about vb.net, but this sounds like an autocommit feature
>>> that's not doing what you expect.
>>>
>>> If nothing else comes to mind, try setting the DB to log all statements
>>> (see log_statement), and compare the resulting trace to what you think
>>> your code is doing. That should at least narrow it down a lot.
>
> I've been able to turn on statement logging (I've set log_statement to
> 'all'), but it doesn't seem to show the begin transaction - commit -
> rollback statements. Is there another way to have them show up in the log?
If they don't show up, they are not being executed at all; which
explains why your transactions "don't roll back", because there are no
transaction blocks defined at all.
--
Alvaro Herrera http://www.advogato.org/person/alvherre
"Oh, great altar of passive entertainment, bestow upon me thy discordant images
at such speed as to render linear thought impossible" (Calvin a la TV)