Re: pgAgent "new step" fails for batch jobs in pgAdmin3 1.10.0 Beta 2

From: Guillaume Lelarge <guillaume(at)lelarge(dot)info>
To: Dave Page <dpage(at)pgadmin(dot)org>
Cc: Kevin Field <kevinjamesfield(at)gmail(dot)com>, pgadmin-hackers(at)postgresql(dot)org
Subject: Re: pgAgent "new step" fails for batch jobs in pgAdmin3 1.10.0 Beta 2
Date: 2009-06-08 21:23:53
Message-ID: 4A2D8169.60506@lelarge.info
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

Dave Page a écrit :
> 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?
>

Actually, it's not really useful in that context. We should simply
disable the checkbox on these dialogs. Perhaps we don't even need an SQL
tab?

Regards.

--
Guillaume.
http://www.postgresqlfr.org
http://dalibo.com

In response to

Responses

Browse pgadmin-hackers by date

  From Date Subject
Next Message Chuck McDevitt 2009-06-09 00:30:26 Re: New patch for bugs in GPDB csv format log handling
Previous Message Dave Page 2009-06-08 21:05:25 Re: New patch for bugs in GPDB csv format log handling