From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
---|---|
To: | GB Clark <postgres(at)vsservices(dot)com> |
Cc: | <pgsql-sql(at)postgresql(dot)org> |
Subject: | Re: Constraint problems |
Date: | 2002-09-27 18:29:34 |
Message-ID: | 20020927112807.D42421-100000@megazone23.bigpanda.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
On Fri, 27 Sep 2002, GB Clark wrote:
> CREATE TABLE sysusers (
> user_id INTEGER DEFAULT nextval('sysusers_user_id_seq')
> UNIQUE NOT NULL PRIMARY KEY,
> username text NOT NULL UNIQUE,
> password text NOT NULL,
>
> createby text NOT NULL DEFAULT 'syscreate',
>
> status char(1) DEFAULT 'A' CHECK (status in ('A', 'I')),
> comment1 text,
> comment2 text,
> tstamp timestamp DEFAULT CURRENT_TIMESTAMP
> );
>
> CREATE UNIQUE INDEX username_unique_idx ON sysusers (username);
>
> INSERT INTO sysusers (username, password, createby) VALUES ('syscreate', 'testing', 'syscreate');
>
> ALTER TABLE sysusers ADD CONSTRAINT createby_test CHECK (createby in (username));
This is only going to check the value of username in the current row.
Why not use a foreign key from createby to username?
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2002-09-27 19:05:49 | PGSQL-Performance mailing list. |
Previous Message | GB Clark | 2002-09-27 18:15:47 | Constraint problems |