Re: [HACKERS] Additional psql requirements

2008-07-25 Thread Tom Lane
Simon Riggs <[EMAIL PROTECTED]> writes: > I just wanted an easy way to write install scripts that work on various > releases/schemas/environments, works on core and on any platform. The word "easy" is out of place in that sentence. Such scripts would likely need information that's entirely outsid

Re: [HACKERS] Additional psql requirements

2008-07-25 Thread Simon Riggs
On Fri, 2008-07-25 at 09:40 +0100, Dave Page wrote: > On Fri, Jul 25, 2008 at 9:36 AM, Pavel Stehule <[EMAIL PROTECTED]> wrote: > > 2008/7/25 Dave Page <[EMAIL PROTECTED]>: > >> On Fri, Jul 25, 2008 at 8:52 AM, daveg <[EMAIL PROTECTED]> wrote: > >> > >>> It seems to me that a sql-like client side

Re: [HACKERS] Additional psql requirements

2008-07-25 Thread Dave Page
On Fri, Jul 25, 2008 at 9:36 AM, Pavel Stehule <[EMAIL PROTECTED]> wrote: > 2008/7/25 Dave Page <[EMAIL PROTECTED]>: >> On Fri, Jul 25, 2008 at 8:52 AM, daveg <[EMAIL PROTECTED]> wrote: >> >>> It seems to me that a sql-like client side scripting language should be as >>> similar as possible to plpg

Re: [HACKERS] Additional psql requirements

2008-07-25 Thread Pavel Stehule
2008/7/25 Dave Page <[EMAIL PROTECTED]>: > On Fri, Jul 25, 2008 at 8:52 AM, daveg <[EMAIL PROTECTED]> wrote: > >> It seems to me that a sql-like client side scripting language should be as >> similar as possible to plpgsql. Pgscript looks a bit like plpgsql, but is >> pretty much incompatible with

Re: [HACKERS] Additional psql requirements

2008-07-25 Thread Dave Page
On Fri, Jul 25, 2008 at 8:52 AM, daveg <[EMAIL PROTECTED]> wrote: > It seems to me that a sql-like client side scripting language should be as > similar as possible to plpgsql. Pgscript looks a bit like plpgsql, but is > pretty much incompatible with it for no particularly obvious reason. pgScrip

Re: [HACKERS] Additional psql requirements

2008-07-25 Thread Pavel Stehule
2008/7/25 Simon Riggs <[EMAIL PROTECTED]>: > > On Fri, 2008-07-25 at 10:00 +0900, ITAGAKI Takahiro wrote: >> Simon Riggs <[EMAIL PROTECTED]> wrote: >> >> > * access to version number >> > * simple mechanism for conditional execution >> > * ability to set substitution variables from command executio

Re: [HACKERS] Additional psql requirements

2008-07-25 Thread daveg
On Fri, Jul 25, 2008 at 08:16:59AM +0100, Simon Riggs wrote: > > On Fri, 2008-07-25 at 10:00 +0900, ITAGAKI Takahiro wrote: > > Simon Riggs <[EMAIL PROTECTED]> wrote: > > > > > * access to version number > > > * simple mechanism for conditional execution > > > * ability to set substitution variab

Re: [HACKERS] Additional psql requirements

2008-07-25 Thread Simon Riggs
On Fri, 2008-07-25 at 10:00 +0900, ITAGAKI Takahiro wrote: > Simon Riggs <[EMAIL PROTECTED]> wrote: > > > * access to version number > > * simple mechanism for conditional execution > > * ability to set substitution variables from command execution > > * conditional execution whether superuser or

Re: [HACKERS] Additional psql requirements

2008-07-24 Thread ITAGAKI Takahiro
Simon Riggs <[EMAIL PROTECTED]> wrote: > * access to version number > * simple mechanism for conditional execution > * ability to set substitution variables from command execution > * conditional execution whether superuser or not Can we use pgScript for such flow controls? http://pgscript.proje

[HACKERS] Additional psql requirements

2008-07-24 Thread Simon Riggs
I have some suggestions for additional psql features. I'm not planning to work on them myself, just proposing them so others can do so if they agree and wish to do so. * default values for substitution values Need a command to set the default value of a substitution variable, so that it takes a sp