From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "Magnus Hagander" <mha(at)sollentuna(dot)net>, <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Re: Query tool result discarding |
Date: | 2006-02-06 09:52:26 |
Message-ID: | E7F85A1B5FF8D44C8A1AF6885BC9A0E40103DEA7@ratbert.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
Thanks, patch applied.
/D
> -----Original Message-----
> From: pgadmin-hackers-owner(at)postgresql(dot)org
> [mailto:pgadmin-hackers-owner(at)postgresql(dot)org] On Behalf Of
> Magnus Hagander
> Sent: 02 February 2006 10:12
> To: pgadmin-hackers(at)postgresql(dot)org
> Subject: [pgadmin-hackers] Query tool result discarding
>
> Hi!
>
>
> A fairly typical use-case for the query tool in my org is:
>
> BEGIN TRANSACTION;
> UPDATE something SET somecol=newval WHERE something=other;
> SELECT * FROM something; -- this is to manually verify results
> ROLLBACK;
>
> Then when everything works, you replace ROLLBACK with COMMIT.
> This works
> perfectly in the query tool in sqlserver, but pgAdmin discards the
> result from SELECT and leaves the result pane empty. Because it's
> overwritten by the empty result from ROLLBACK.
>
> Attached patch fixes this very limited test case. I'm well enough
> unfamiliar with that code that I think it's probably not the correct
> solution "in the big scheme" (and it also seems too easy),
> but it might
> help point one of you guys who know that code better in the right
> direction. Or on the off chance that it's right, hey, there was some
> luck left over :-)
>
> //Magnus
>
From | Date | Subject | |
---|---|---|---|
Next Message | svn | 2006-02-06 10:12:52 | SVN Commit by dpage: r4987 - in trunk/pgadmin3: . src/base src/frm src/include/base |
Previous Message | svn | 2006-02-06 09:52:14 | SVN Commit by dpage: r4986 - in trunk/pgadmin3: . src/base |