| From: | "Aasmund Midttun Godal" <postgresql(at)envisity(dot)com> |
|---|---|
| To: | hherb(at)malleenet(dot)net(dot)au |
| Cc: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: constraint via selection |
| Date: | 2001-11-17 19:09:59 |
| Message-ID: | 20011117190959.23001.qmail@ns.krot.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
I don't know much about this issue. but perhaps, since I assume the country codes are static, it would be faster if you just checked each individual value (especially if there are few of them) like so
CHECK code = 'no' OR code = 'de' OR code = 'se', etc.
I don't know.
Regards,
Aasmund.
On Sun, 18 Nov 2001 00:00:57 +1100, Horst Herb <hherb(at)malleenet(dot)net(dot)au> wrote:
>
> Sorry, I probably should reformulate my question into "is there a more
> effficient constraint than a foreign key constraint for this simple
> problem"?
>
> Horst
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
Aasmund Midttun Godal
aasmund(at)godal(dot)com - http://www.godal.com/
+47 40 45 20 46
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephan Szabo | 2001-11-17 21:06:14 | Re: constraint via selection |
| Previous Message | Masaru Sugawara | 2001-11-17 13:30:09 | Re: Optimization, etc |