| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | josh(at)agliodbs(dot)com |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Constraints & pg_dump |
| Date: | 2004-03-17 17:03:35 |
| Message-ID: | 25947.1079543015@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Josh Berkus <josh(at)agliodbs(dot)com> writes:
> What about table-level check constraints? Seems like one of those should be
> able to be used to check a vertical assertion within a table. Or do we need
> SQL ASSERTION for this?
Seems like it would be smart to maintain a syntactic distinction between
row-local checks and global checks, so I'd be inclined to insist on
using ASSERTION. I am not sure what the SQL spec has to say about this
though --- they probably have some obscure phraseology that bears on the
question.
AFAIR, whether a constraint is syntactically attached to a column or is
"loose" in the table definition is not supposed to have any semantic
consequences, but I might be wrong about that too.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2004-03-17 17:12:59 | Re: Constraints & pg_dump |
| Previous Message | Bruce Momjian | 2004-03-17 17:02:11 | Re: [HACKERS] Index creation takes for ever |