| From: | Christoph Zwerschke <cito(at)online(dot)de> |
|---|---|
| To: | Ashesh Vashi <ashesh(dot)vashi(at)enterprisedb(dot)com>, Dave Page <dpage(at)pgadmin(dot)org> |
| Cc: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
| Subject: | Re: Fix for a problem with auto reconnection |
| Date: | 2014-06-22 14:57:21 |
| Message-ID: | 53A6EED1.1050506@online.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers |
Thanks for looking into this. The problem with the wrong encoding is now
gone, but another problem appeared:
When the connection is reestablished, I get an additional alert with an
error message "Column not found in pgSet: "datlastsysoid".
The problem seems to be that needColQuoting is not reset to false in the
Reset() method as it is done in the Reconnect() method.
Wenn I add the line "needColQuoting = false" before the call to
Initialize() in the Reset() method, everything works as expected.
-- Christoph
Am 17.06.2014 08:35, schrieb Ashesh Vashi:
> Dave,
>
> PFA - moved the initialisation code in a separate function, and called
> that function from the "Reset" function too.
> Please take a look at it.
>
>
> --
>
> Thanks & Regards,
>
> Ashesh Vashi
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dmitriy Olshevskiy | 2014-06-22 18:13:49 | PATCH: don't save empty favourite queries |
| Previous Message | Dmitriy Olshevskiy | 2014-06-22 10:29:26 | PATCH: save and restore the settings of the search objects dialog |