From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
Cc: | pgpool-general(at)pgfoundry(dot)org, Leonardo Carvalho <leonardotcarvalho(at)gmail(dot)com>, "Kostas P(dot)" <kostas(at)nsoft(dot)lt>, pgadmin-hackers(at)postgresql(dot)org |
Subject: | Re: [Pgpool-general] backend mismatch |
Date: | 2009-07-20 15:50:53 |
Message-ID: | 937d27e10907200850k5fef01d7l45d8cb1b5898e2ad@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
On Thu, Jul 16, 2009 at 3:38 PM, Guillaume
Lelarge<guillaume(at)lelarge(dot)info> wrote:
> Le jeudi 16 juillet 2009 à 15:48:58, Leonardo Carvalho a écrit :
>> Unfortunately, PgAdmin always sends this commands , trying to use
>> ISO date format.
>> If you discover how to fix that in PgAdmin, tell us!
>>
>
> There's no way to fix that without recompiling. But you can try the patch
> attached.
>
> I CC-ed pgadmin-hackers list so Dave can grab and check my patch :)
Looks OK to me. What's the problem though - the SET, or having
multiple command in one SQL query? If it's the latter, then that
happens in a bunch of other places where it can't be fixed so easily.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Guillaume Lelarge | 2009-07-20 16:38:56 | Re: [Pgpool-general] backend mismatch |
Previous Message | Guillaume Lelarge | 2009-07-19 21:42:50 | Re: Re: [pgadmin-support] pgAdmin3 Version 1.10.0 : Crash when configuring an pgAgent job |