From: | "pgAdmin Trac" <trac(at)code(dot)pgadmin(dot)org> |
---|---|
To: | |
Cc: | pgadmin-hackers(at)postgresql(dot)org |
Subject: | Re: [pgAdmin III] #47: Savepoints in PgAdmin |
Date: | 2009-08-21 07:50:47 |
Message-ID: | 062.d807a9bcbd0183bd7b375bb631727ea2@code.pgadmin.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
#47: Savepoints in PgAdmin
---------------------------+------------------------------------------------
Reporter: Cédric DUPREZ | Owner: dpage
Type: bug | Status: new
Priority: minor | Milestone: 1.10.1
Component: pgadmin | Version: 1.8
Keywords: querytool | Platform: all
---------------------------+------------------------------------------------
Comment(by gleu):
If it fails, pgAdmin automatically does a ROLLBACK. In the
frmQuery::completeQuery() method, there is this code:
// If the transaction aborted for some reason, issue a rollback to
cleanup.
if (conn->GetTxStatus() == PGCONN_TXSTATUS_INERROR)
conn->ExecuteVoid(wxT("ROLLBACK;"));
We should perhaps have an option to enable/disable this behaviour
--
Ticket URL: <http://code.pgadmin.org/trac/ticket/47#comment:1>
pgAdmin III <http://code.pgadmin.org/trac/>
pgAdmin III
From | Date | Subject | |
---|---|---|---|
Next Message | PESTY Benoit | 2009-08-21 09:33:59 | Background color in query tool |
Previous Message | pgAdmin Trac | 2009-08-21 07:49:56 | [pgAdmin III] #47: Savepoints in PgAdmin |