From: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de> |
---|---|
To: | Magnus Hagander <mha(at)sollentuna(dot)net> |
Cc: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Re: select inside transactions |
Date: | 2006-02-23 16:39:40 |
Message-ID: | 43FDE54C.6070304@pse-consulting.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
Magnus Hagander wrote:
>>>>I had to revert the patch on pgSetBase.cpp (Rev4986)
>>
>>because to handle
>>
>>>>the very special case of selects inside transactions when
>>
>>executed in
>>
>>>>a single step (I'd recommend to execute them step by step) the
>>>>standard case of a query returning no data (e.g. drop table foo)
>>>>didn't return messages any more.
>>>
>>>
>>>Yikes. I guess my disclaimer was well placed ;-)
>>>
>>>Did you just revert it, or did you figure out a proper way
>>
>>of doing it?
>>
>>Just reverted. Currently I don't see a proper way to implement it,
>>unless multiple output panes (as in isqlw) are implemented.
>
>
> Bummer. I had that feeling - it seemed to easy :-(
You could try to store the last result (for later returning), and drop
it if a newer is detected. Please take care that return code of *all*
commands are reported.
Regards,
Andreas
From | Date | Subject | |
---|---|---|---|
Next Message | Edward Di Geronimo Jr. | 2006-02-23 19:21:01 | Re: Query tool results in grid |
Previous Message | Andreas Pflug | 2006-02-23 16:21:11 | Re: pgAdmin server properties dialog |