Re: By Passed Domain Constraints
От | Tom Lane |
---|---|
Тема | Re: By Passed Domain Constraints |
Дата | |
Msg-id | 27039.1120665958@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: By Passed Domain Constraints (Robert Perry <rlperry@lodestonetechnologies.com>) |
Ответы |
Re: By Passed Domain Constraints
Re: [HACKERS] By Passed Domain Constraints |
Список | pgsql-interfaces |
Robert Perry <rlperry@lodestonetechnologies.com> writes: > I have also been bitten by the problem you are describing. But, > that one is a problem even when called from psql if I am not > mistaken. Does psql not use pqlib? Perhaps it is something about > PQexecParams that is the problem. I will test in a little while. [ thinks about it... ] If you've declared the function input parameter as a domain type and then write a parameterized query like... function($1) ... and don't specify any particular datatype for the parameter symbol, I think the backend will infer the domain type as the parameter type. Which would also allow bypassing the domain checks. You could work around this by explicitly specifying the parameter type as text or varchar or whatever the domain's base type is. I wonder though if we oughtn't change the backend so that the inferred type of a parameter symbol is never a domain, but the domain's base type. That would force the proper application of CoerceToDomain inside the constructed query parsetree. regards, tom lane
В списке pgsql-interfaces по дате отправления: