From: | "Dave Page" <dpage(at)postgresql(dot)org> |
---|---|
To: | "Guillaume Lelarge" <guillaume(at)lelarge(dot)info> |
Cc: | pgadmin-hackers(at)postgresql(dot)org |
Subject: | Re: Enabling SQL text field in the SQL tab of object dialog |
Date: | 2008-06-16 20:12:58 |
Message-ID: | 937d27e10806161312s4d6e6a82r39f333eb13beae9f@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
On Mon, Jun 16, 2008 at 9:11 PM, Dave Page <dpage(at)postgresql(dot)org> wrote:
> Hmm, I'd forgotten about that. We do it because it allows us to run
> non-transaction safe DDL in separate transactions (which is required
> in 8.3). Actually, this is not a major issue - all that will happen is
> that the server will reject the SQL in 8.3+ if the user includes no
> transaction safe DDL with other commands (or blindly accept it in
> earlier versions). I say we just split the text control on those two
> dialogues, per option 1.
Hmm, just to add - we could always include a comment in the GetSQL()
output to explain why the first statement is separate from the rest.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2008-06-16 20:15:55 | Re: A fix and a new functionnality for the colour patch |
Previous Message | Dave Page | 2008-06-16 20:11:42 | Re: Enabling SQL text field in the SQL tab of object dialog |