Re: proposal: custom variables management - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: proposal: custom variables management
Date
Msg-id BAY20-F1749A84B2FCAAA2502633EF9840@phx.gbl
Whole thread Raw
In response to Re: proposal: custom variables management  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: proposal: custom variables management  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
>
>ISTM you are trying to do too much. We need to get the base functionality, 
>as described by Tom in the thread I referred you to, working first. Extra 
>stuff could be added later if necessary.
>
>cheers
>

I don't wont to build cathedral. Now is time for discussion, no? I am 
collect any arguments. With "enhanced" custom variables we can fill modules 
hole in plpgsql or any pl. With it security definer's procedures in any 
languages can safety share values. I worked on large wramework designed for 
plpgsql, and we had to store some temp values in temporary tables. Safe 
custom variables can be solution. It's only idea, nothing more.

Regards
Pavel Stehule

_________________________________________________________________
Najdete si svou lasku a nove pratele na Match.com. http://www.msn.cz/



pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: proposal: custom variables management
Next
From: Mark Kirkwood
Date:
Subject: Re: Bug: Buffer cache is not scan resistant