Re: Sanitize schema name
| От | Ludovic Gasc | 
|---|---|
| Тема | Re: Sanitize schema name | 
| Дата | |
| Msg-id | CAON-fpELTeEZckCejE9+Eq-Q0aj9GHakffhNRUu41cXvHRD36g@mail.gmail.com обсуждение исходный текст | 
| Ответ на | Re: Sanitize schema name ("P. Christeas" <xrg@linux.gr>) | 
| Ответы | Re: Sanitize schema name | 
| Список | psycopg | 
2015-05-10 11:00 GMT+02:00 P. Christeas <xrg@linux.gr>:
 
 
On Thursday 07 of May 2015, Daniele Varrazzo wrote:
> Looks like there is more and more the need of exposing a function like
> libpq's PQescapeIdentifier [1]. Too bad psycopg 2.6 has been released
> so recently, I'm reluctant to add such a function to 2.6.1.
>
> Maybe releasing a small Python module exposing just that function,
> then add the functionality to psycopg 2.7?
I vote for a pre-release of 2.7, with this feature. Modifying the API, even if
the new function wouldn't interfere with any existing ones, calls for a
version bump.
I'm in to be one of a beta-tester.
Just another idea, would it make sense to abuse the semantics of string
formatting[1] and introduce another type, say "%t" [2] for implicit identifier
escaping?
This would make our queries look like:
cr.execute("SELECT id FROM %t WHERE name = %s", ('some.tbl', 'spam'))
Sincerely, it should be awesome, because it means it's more end-developer friendly.
If you also support %(key)t syntax it should be wonderful, because we use dict to fill query values, easier to write.
[1] https://docs.python.org/2/library/stdtypes.html#string-formatting
[2] I notice that "t" isn't used for anything else, so far.
--
Sent via psycopg mailing list (psycopg@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/psycopg
В списке psycopg по дате отправления: