| From: | Sergiy Vyshnevetskiy <serg(at)vostok(dot)net> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | pgsql-bugs(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: BUG #2948: default null values for not-null domains |
| Date: | 2007-02-01 15:04:43 |
| Message-ID: | Pine.LNX.4.64.0702011650090.22446@uanet.vostok.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Thu, 1 Feb 2007, Peter Eisentraut wrote:
> Tom Lane wrote:
>> I'm starting to get the feeling that the entire idea of NOT NULL
>> domains is broken :-(
>
> How is that so very different from having a default value of 5 with a
> domain that rejects 5?
Because 5 will be rejected as a value for a variable or field of such
domain. This is correct (and useful) behavior.
On the other hand null can make it there under some circumstances, even if
domain explicitly forbids nulls. Which is the bug I'm fighting against.
Actually there are several of them, and I plan to post them all. And,
hopefully, bugfixes too.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sergiy Vyshnevetskiy | 2007-02-01 15:43:55 | BUG #2954: null is not checked against domain constraints in return clause |
| Previous Message | Tom Lane | 2007-02-01 14:33:48 | Re: BUG #2948: default null values for not-null domains |