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

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search for
  Advanced Search

Re: Domains as Subtypes


  • From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
  • To: elein <elein(at)varlena(dot)com>
  • Cc: Jim Nasby <jnasby(at)pervasive(dot)com>, josh(at)agliodbs(dot)com, pgsql-hackers(at)postgresql(dot)org
  • Subject: Re: Domains as Subtypes
  • Date: Mon, 27 Mar 2006 11:41:30 -0500
  • Message-id: <15135(dot)1143477690(at)sss(dot)pgh(dot)pa(dot)us>

elein <elein(at)varlena(dot)com> writes:
> But I like the idea of centralizing the check in the input/output
> functions.  It seems clearer and cleaner.

I remembered the problem with doing it that way: an input function can't
enforce a domain NOTNULL constraint, because it won't even get invoked
for a null input value.  So there seems no way around having a special
case for domains in all places where I/O conversion is done.

			regards, tom lane



Home | Main Index | Thread Index

Privacy Policy | PostgreSQL Archives hosted by Command Prompt, Inc. | Designed by tinysofa
Copyright © 1996 – 2008 PostgreSQL Global Development Group