From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Perry <rlperry@lodestonetechnologies.com>
Cc: pgsql-interfaces@postgresql.org, Bruce Momjian <pgman@candle.pha.pa.us>
Subject: Re: By Passed Domain Constraints
Date: Wed, 06 Jul 2005 10:35:37 -0400
Message-ID: <26103.1120660537@sss.pgh.pa.us> (raw)
In-Reply-To: <61C4410A-F2CE-49E9-92BA-1BDF89818DAA@lodestonetechnologies.com>
References: <61C4410A-F2CE-49E9-92BA-1BDF89818DAA@lodestonetechnologies.com>
Robert Perry <rlperry@lodestonetechnologies.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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: tgl@sss.pgh.pa.us, rlperry@lodestonetechnologies.com, pgman@candle.pha.pa.us
Subject: Re: By Passed Domain Constraints
In-Reply-To: <26103.1120660537@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox