Skip site navigation (1) Skip section navigation (2)

Re: show() function

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Joe Conway <mail(at)joeconway(dot)com>, <pgsql-patches(at)postgresql(dot)org>
Subject: Re: show() function
Date: 2002-06-26 20:44:49
Message-ID: Pine.LNX.4.44.0206261834430.838-100000@localhost.localdomain (view raw, whole thread or download thread mbox)
Lists: pgsql-patches
Tom Lane writes:

> I was actually alluding to the possibility of a *writable* table, eg
> 	UPDATE pg_settings SET value = 'true' WHERE name = 'debug_print_query';
> as a query-language equivalent of
> 	SET debug_print_query = true;

I think this can be done with a stored procedure.  Magic tables with
side-effects seem weird.

Is there anything fundamentally difficult with supporting "PROCEDURE
foo()" as equivalent with "FUNCTION foo() RETURNS opaque" and "CALL foo()"
as equivalent with "SELECT foo()" and throw away the result.  Then you
could define a function analogous to SHOW and a procedure analogous to SET
and can manipulate the values using the full expression language.

Peter Eisentraut   peter_e(at)gmx(dot)net

In response to


pgsql-patches by date

Next:From: Peter EisentrautDate: 2002-06-26 20:45:39
Subject: Re: show() function
Previous:From: Manfred KoizarDate: 2002-06-26 14:38:47
Subject: Re: [HACKERS] Page OpaqueData

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group