From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | Kevin Field <kevinjamesfield(at)gmail(dot)com> |
Cc: | pgadmin-hackers(at)postgresql(dot)org |
Subject: | Re: pgAgent "new step" fails for batch jobs in pgAdmin3 1.10.0 Beta 2 |
Date: | 2009-05-11 15:13:36 |
Message-ID: | 937d27e10905110813u290690dfg8162e4389ba32c98@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
On Mon, May 11, 2009 at 3:43 PM, Kevin Field <kevinjamesfield(at)gmail(dot)com> wrote:
>
> About editing, I just tried this in the win32 beta3, and it still
> ignores the changes you make: I went to create a new job step,
> selected batch, typed gibberish in the name and definition, unchecked
> 'read only', and erased the generated SQL and replaced it with "select
> 'hello'", and then clicked OK, and it added the gibberish step (rather
> than doing nothing, which is what select-hello should've done...) So
> 'read only' doesn't seem to be useful at this point.
Oh, I see what you mean. If memory serves, the pgAgent dialogues
process their SQL in a slightly different way to all the other
dialogues because they need to run some parts in different steps.
Guillaume; this is your code ( :-p ) - do you see a simple way to fix
it, or should the checkboxes be disabled on the three pgAgent
dialogues?
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | svn | 2009-05-11 22:29:08 | SVN Commit by guillaume: r7862 - trunk/pgadmin3/i18n/pl_PL |
Previous Message | Kevin Field | 2009-05-11 14:43:29 | Re: pgAgent "new step" fails for batch jobs in pgAdmin3 1.10.0 Beta 2 |