Re: undefined behaviour for sub-transactions?

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Greg Stark <gsstark(at)mit(dot)edu>
Cc: Jaime Casanova <systemguards(at)gmail(dot)com>, Tyler MacDonald <tyler(at)yi(dot)org>, Andrew Sullivan <ajs(at)crankycanuck(dot)ca>, Tim Bunce <Tim(dot)Bunce(at)pobox(dot)com>, Jochen Wiedmann <jochen(dot)wiedmann(at)gmail(dot)com>, Paul DuBois <paul(at)snake(dot)net>, dbi-users(at)perl(dot)org, perl(at)lists(dot)mysql(dot)com, pgsql-general(at)postgresql(dot)org
Subject: Re: undefined behaviour for sub-transactions?
Date: 2005-12-01 18:12:15
Message-ID: 438F3CFF.50006@commandprompt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


>Where is Postgres at with psql using savepoints implicitly to wrap every
>client command btw? My single biggest pet peeve with Postgres is that setting
>autocommit off in psql is basically unusable because any typo forces you to
>start your transaction all over again.
>
>
Going to have to disagree with you here. I use it all day long ;). If I
need a savepoint, I define one.

Joshua D. Drake

--
The PostgreSQL Company - Command Prompt, Inc. 1.503.667.4564
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
Managed Services, Shared and Dedicated Hosting
Co-Authors: PLphp, PLperl - http://www.commandprompt.com/

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Jaime Casanova 2005-12-01 18:21:00 Re: Question
Previous Message Jaime Casanova 2005-12-01 18:08:59 Re: Disk Keeper