[HACKERS] proposal: schema variables - Mailing list pgsql-hackers
From | Pavel Stehule |
---|---|
Subject | [HACKERS] proposal: schema variables |
Date | |
Msg-id | CAFj8pRDY+m9OOxfO10R7J0PAkCCauM-TweaTrdsrsLGMb1VbEQ@mail.gmail.com Whole thread Raw |
Responses |
Re: [HACKERS] proposal: schema variables
Re: [HACKERS] proposal: schema variables Re: [HACKERS] proposal: schema variables Re: [HACKERS] proposal: schema variables Re: [HACKERS] proposal: schema variables Re: [HACKERS] proposal: schema variables Re: [HACKERS] proposal: schema variables Re: [HACKERS] proposal: schema variables Re: [HACKERS] proposal: schema variables Re: [HACKERS] proposal: schema variables |
List | pgsql-hackers |
Hi,
I propose a new database object - a variable. The variable is persistent object, that holds unshared session based not transactional in memory value of any type. Like variables in any other languages. The persistence is required for possibility to do static checks, but can be limited to session - the variables can be temporal. [ ON TRANSACTION END { RESET | DROP } ]
[ { VOLATILE | STABLE } ];
The variables should be used in queries implicitly (without JOIN)
SELECT varname;
The SEARCH_PATH is used, when varname is located. The variables can be used everywhere where query parameters are allowed.
I hope so this proposal is good enough and simple.
Comments, notes?
regards
Pavel
pgsql-hackers by date: