From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Andrew Chernow <ac(at)esilo(dot)com> |
Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: named parameters in SQL functions |
Date: | 2009-11-15 19:16:20 |
Message-ID: | 162867790911151116o322d5844l8c4bb542424f69ad@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2009/11/15 Andrew Chernow <ac(at)esilo(dot)com>:
>
>>> I like the special marker idea. A '$' would be nice because its already
>>> in
>>> use for similar purposes, but I think that would lead to ambiguity with
>>> dollar quoting.
>>
>> no, it should be safe (if you don't use for dollar quoting some like
>> $variablename$)
>>
>
> Actually, I was thinking of something like $abc$def, where abc and def are
> variables. Although, this is much less likely than column name conflicts.
>
> Other possibles are: $(var), @var@, or %var%. I'd perfer a single character
> marker but that may not fly.
>
single character is my preference too.
Pavel
> --
> Andrew Chernow
> eSilo, LLC
> every bit counts
> http://www.esilo.com/
>
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2009-11-15 19:20:58 | Re: Summary and Plan for Hot Standby |
Previous Message | Andrew Chernow | 2009-11-15 19:13:56 | Re: named parameters in SQL functions |