I recently posted a notice publicising the pgAdmin Development Team's
intent to change the licence of pgAdmin from the Artistic Licence v1.0
to v2.0 in order to address ambiguities with the original text.
Unfortunately we were unable to change the licence as we had hoped,
and in order to resolve t
Hi pgAdmin hackers,
Here is a patch for pgAdmin. I have finally completed the patch for
the pgScript outputs and am sorry for the delay.
This patch also corrects a bug in pgsPrintStmt.cpp because of a thread
double lock in case of exception.
I have other updates to send but I would like this one t
On Fri, Mar 6, 2009 at 7:31 PM, Mickael Deloison wrote:
> Hi pgAdmin hackers,
>
> Here is a patch for pgAdmin. I have finally completed the patch for
> the pgScript outputs and am sorry for the delay.
> This patch also corrects a bug in pgsPrintStmt.cpp because of a thread
> double lock in case of
> -Original Message-
> From: Dave Page [mailto:dp...@pgadmin.org]
> Sent: Friday, March 06, 2009 7:08 AM
> To: Chuck McDevitt
> Cc: pgadmin-hackers
> Subject: Greenplum patch for pgAdmin
>
> Hi Chuck,
>
> I've spent the last few hours working on your patches to pgAdmin. I've
> fixed/cle
I will work on this over the weekend, and get a new patch to you Monday evening
> -Original Message-
> From: Dave Page [mailto:dp...@pgadmin.org]
> Sent: Friday, March 06, 2009 7:08 AM
> To: Chuck McDevitt
> Cc: pgadmin-hackers
> Subject: Greenplum patch for pgAdmin
>
> Hi Chuck,
>
> I'v
On Fri, Mar 6, 2009 at 9:41 PM, Chuck McDevitt wrote:
> I will work on this over the weekend, and get a new patch to you Monday
> evening
Thanks.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
--
Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org)
To make chan
2009/3/6 Dave Page :
> There were some cases where error messages would be lost, and part of
> the fix was to try to make errors all go through SetLastResultError()
> for consistency in output. I modified SetLastResultError() so that if
> it's passed NULL, it gets the message via: lastResultError.m
Sorry - I meant some pgScript code that would create a message so i
can figure out where it gets lost.
On 3/6/09, Mickael Deloison wrote:
> 2009/3/6 Dave Page :
>> There were some cases where error messages would be lost, and part of
>> the fix was to try to make errors all go through SetLastResu
2009/3/6 Dave Page :
> Sorry - I meant some pgScript code that would create a message so i
> can figure out where it gets lost.
>> Here is the code you requested, I removed the useless parts:
>>
>> pgQueryThread thread(m_app->connection(), stmt);
>>
>> if (thread.Create() == wxTHREAD_NO_ERROR)
>> {
