From: David Garamond <lists@zara.6.isreserved.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: constraint and ordered value
Date: Fri, 30 Dec 2005 00:48:26 +0700
Message-ID: <43B4216A.3080707@zara.6.isreserved.com> (raw)
In-Reply-To: <0BC6CA83-B17E-47CC-8438-013D6B7348ED@eddl.us>
References: <43B17F52.7000305@zara.6.isreserved.com>
<20051229071625.GA2815@wolff.to>
<0BC6CA83-B17E-47CC-8438-013D6B7348ED@eddl.us>
Daryl Richter wrote:
>> No. A constraint only applies to one row at a time. If you try to
>> work around
>> this by calling a function that does queries it isn't guarenteed to
>> work.
>> And if you are thinking of calling a function that does a query, you
>> aren't
>> looking at saving time over using triggers.
>>
>> Also, if you are going to have concurrent updates, you are going to
>> need to
>> do table locking to make this work.
>
> And, finally, you should ask yourself *why* are you doing this, given
> that one of the fundamental properties of a table (relation) is that
> the rows (tuples) are *unordered.* So much of what makes a relational
> db a wonderful thing for storing data depends on this notion.
>
> If you provide an explanation of what you are trying to model, perhaps
> we can help you find a better schema design.
Thanks for the insightful answers. Actually I'm just learning about and
trying out CHECK constraints in Postgres (and Firebird) :-)
Regards,
dave
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-sql@postgresql.org
Cc: lists@zara.6.isreserved.com
Subject: Re: constraint and ordered value
In-Reply-To: <43B4216A.3080707@zara.6.isreserved.com>
* 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