SOLVED: I should use the "CREATE UNIQUE INDEX ... ON ..." command, on an
existing table. This cannot be done inline within the CREATE TABLE command.
Thanks all, for your help.
Rob
2010/12/28 InterRob
> Dear Tom,
>
> Thanks for your hints; it is indeed funny (as mentioned by Guillaume) how
> i
Dear Tom,
Thanks for your hints; it is indeed funny (as mentioned by Guillaume) how
indexes and constraints are being mixed up -- mentioned either in the
Indexes or in Constraints department. Pgsql and PgAdmin make different
choices here. And well, given their implementation these choices can both
Le 27/12/2010 22:02, Richard Broersma a écrit :
> On Mon, Dec 27, 2010 at 12:50 PM, InterRob wrote:
>> pgsql Command "\d test" produces the following:
>>Table "public.test"
>>Column | Type | Modifiers
>> +-+---
>> object_id | integer |
>> subject_id
Richard Broersma writes:
> On Mon, Dec 27, 2010 at 12:50 PM, InterRob wrote:
>> pgsql Command "\d test" produces the following:
>>Table "public.test"
>>Column | Type | Modifiers
>> +-+---
>> object_id | integer |
>> subject_id | integer |
>> Indexes
On Mon, Dec 27, 2010 at 12:50 PM, InterRob wrote:
> pgsql Command "\d test" produces the following:
> Table "public.test"
> Column | Type | Modifiers
> +-+---
> object_id | integer |
> subject_id | integer |
> Indexes:
> "EXCL_double_combi" EXCLUDE
Sorry: that is because the major part of my E-mail got chopped off...
Herewith I am resending it:
---
Dear list,
To rule out any double combination of two identifiers, in any order, I
applied the following constraint to a table:
CREATE TABLE test(
o
On Mon, Dec 27, 2010 at 8:31 AM, Rob Marjot wrote:
> Dear list,
> To rule out any double combination of two identifiers, in any order, I
> applied the following constraint to a table:
> CREATE TABLE test(object_id INTEGER, subject_id INTEGER, CONSTRAINT
I don't see the definition of your constrai
Dear list,
To rule out any double combination of two identifiers, in any order, I
applied the following constraint to a table:
CREATE TABLE test(object_id INTEGER, subject_id INTEGER, CONSTRAINT
Dear list,
To rule out any double combination of two identifiers, in any order, I
applied the following constraint to a table:
CREATE TABLE test(
object_id INTEGER,
subject_id INTEGER,
CONSTRAINT "EXCL_double_combi" EXCLUDE USING btree (imm_LEAST(subject_id,
object_id) WITH =, imm_GREATEST(
