Re: Bug#347548: DOMAIN CHECK constraint bypassed

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-bugs(at)postgresql(dot)org, 347548-forwarded(at)bugs(dot)debian(dot)org
Subject: Re: Bug#347548: DOMAIN CHECK constraint bypassed
Date: 2006-01-28 19:30:44
Message-ID: 19098.1138476644@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> This bug was reported to Debian. Comments?

These are all known issues. The implementation of domains really needs
rather a lot of work :-(.

One thing we might think about is having domain types use a special set
of input functions rather than just linking directly to the base-type
functions (kinda like arrays use array_in, etc). These functions could
then be charged with applying the appropriate constraint checks after
invoking the correct base-type input function. I'm not sure about
performance issues (ie, how to avoid repetitive lookups and memory
leaks) but at least we'd only need to solve it in one place and not
several.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2006-01-29 05:25:59 Re: BUG #2218: Variables selected in VIEWs under different names break queries using those views
Previous Message Peter Eisentraut 2006-01-28 19:17:17 Re: Bug#347548: DOMAIN CHECK constraint bypassed