| From: | "Pavel Stehule" <pavel(dot)stehule(at)hotmail(dot)com> |
|---|---|
| To: | andrew(at)dunslane(dot)net |
| Cc: | tgl(at)sss(dot)pgh(dot)pa(dot)us, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: proposal: custom variables management |
| Date: | 2007-03-05 22:02:56 |
| Message-ID: | BAY20-F1749A84B2FCAAA2502633EF9840@phx.gbl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Kirkwood | 2007-03-05 22:07:51 | Re: Bug: Buffer cache is not scan resistant |
| Previous Message | Andrew Dunstan | 2007-03-05 21:42:57 | Re: proposal: custom variables management |