Re: pgScript patch based on pgScript-1.0-beta-3

From: "Erikjan Rijkers" <er(at)xs4all(dot)nl>
To: "Mickael Deloison" <mdeloison(at)gmail(dot)com>
Cc: pgadmin-hackers(at)postgresql(dot)org
Subject: Re: pgScript patch based on pgScript-1.0-beta-3
Date: 2008-08-16 16:08:11
Message-ID: 20770.156.83.0.124.1218902891.squirrel@webmail.xs4all.nl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

On Sat, August 16, 2008 15:55, Mickael Deloison wrote:
> 2008/8/14 Erikjan Rijkers <er(at)xs4all(dot)nl>:
>> 1) It would be nice if pgScript would only execute a select-block, like the
>> normal pgAdmin querytool does.
>
> Do you mean: redirecting a pgScript script to the regular query tool
> if both the pgScript button is pressed and the edit window contains
> only a select statement?

No.

In the regular query tool one can draw a select block (with mouse or
keyboard). Subsequently pressing F5 *only* executes the selected text. This
is a very handy behaviour that (I think) could be mimicked by pgscript without
problem.
(it makes it easy to quickly test parts of a larger script.)

>> 2) The example script from the url above says:
>> IF (SELECT 1 FROM table) -- Then table exists

> You're right, with a count(*) it returns something (0 if no rows) and
> this is true.

Right, thanks.

>> 3) When the BEGIN - END block fails, pgScript executes the ELSE block.
>> This
>> seems questionable behaviour, no? It can be seen with that same
> I do not understand this observation. Could you be more precise please?

Upon consideration, I might have been mistaken; I'll test again and look for
a clearly reproducible case.

thanks,

Erikjan

Responses

Browse pgadmin-hackers by date

  From Date Subject
Next Message Mickael Deloison 2008-08-16 17:36:00 Re: pgScript patch based on pgScript-1.0-beta-3
Previous Message Mickael Deloison 2008-08-16 15:07:07 Re: pgScript patch based on pgScript-1.0-beta-3