Skip site navigation (1) Skip section navigation (2)

Re: By Passed Domain Constraints

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Perry <rlperry(at)lodestonetechnologies(dot)com>
Cc: pgsql-interfaces(at)postgresql(dot)org,Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Subject: Re: By Passed Domain Constraints
Date: 2005-07-06 14:35:37
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackerspgsql-interfaces
Robert Perry <rlperry(at)lodestonetechnologies(dot)com> writes:
>      It looks like the data is not checked when passed to the  
> function and from their on out since it is already the correct type  
> it is not checked again. Has anyone else seen something like this?

IIRC, plpgsql does not know anything about domains and does not enforce
domain constraints when assigning to local variables or the function
result.  The same is true of the other PLs, though I think it could only
matter for the function result in those cases (internal variables aren't
of SQL types anyway for them).  You could probably work around this by
writing explicit casts to the domain inside the function, eg
"RETURN x::domain" not just "RETURN x".

I thought the unfinished work for domains was mentioned on the TODO list
but I don't see anything about it right now.

			regards, tom lane

In response to


pgsql-hackers by date

Next:From: Bruce MomjianDate: 2005-07-06 14:45:13
Subject: Re: Disable page writes when fsync off, add GUC
Previous:From: Tom LaneDate: 2005-07-06 14:29:26
Subject: Re: timezone changes break windows and cygwin

pgsql-interfaces by date

Next:From: Robert PerryDate: 2005-07-06 15:43:06
Subject: Re: By Passed Domain Constraints
Previous:From: Robert PerryDate: 2005-07-06 13:49:27
Subject: By Passed Domain Constraints

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group