Search Postgresql Archives

Re: Using the dollar sign as a prefix for named parameter of prepared statement.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Dmitry Igrishin <dmitigr@xxxxxxxxx> writes:
> I'm working on finishing beta release of my C++ API for PostgreSQL. The
> library
> have simple SQL parser (preprocessor) to support the queries like that:

>   SELECT :"column", $tag$constant string$tag$
>     FROM :tables
>     WHERE name LIKE :'name' AND
>           sex = $1 AND
>           age > $age

>   where:
>     :"column" is a variable which will be quoted as identifier (like in
> psql),
>     :tables is a variable which will be not be quoted at all (like in psql),
>     :'name' is a variable which will be quoted as literal (like in psql),
>     $1 is a positional parameter,
>     $age is a named parameter

> Is there are any contraindications/caveats/gotchas on using the dollar sign
> as a prefix for the named parameters?

How are you going to distinguish named parameters from dollar-quote tags?
For instance, this is legal:

regression=# select $foobar$stuff$foobar$;
 ?column? 
----------
 stuff
(1 row)

I think you're going to end up with weird corner case behaviors if
you try to squeeze still another meaning into "$letters..."

			regards, tom lane


-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general



[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]

  Powered by Linux