| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
| Cc: | "Thomas Lockhart" <lockhart(at)fourpalms(dot)org>, "PostgreSQL Hackers List" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Suggestions for implementing IS DISTINCT FROM? |
| Date: | 2002-06-24 13:42:18 |
| Message-ID: | 17512.1024926138@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> writes:
> Should I use a boolean in the node to indicate whether it is SYMMETRIC or
> ASYMMETRIC, or should I use some sort of integer to indicate whether it is
> SYMMETRIC, ASYMMETRIC or DEFAULT (ASYMMETRIC). That way the reverse in
> rules and views could leave out the ASYMMETRIC if it wasn't specified
> originally, rather than always adding it in. Which is better?
My intention is to reverse-list as either "BETWEEN" or "BETWEEN SYMMETRIC".
While I believe in reproducing the source text during reverse listing,
I don't take it to extremes ;-)
So a boolean is sufficient.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marc G. Fournier | 2002-06-24 14:02:32 | Re: pgadmin.postgresql.org displaying errors |
| Previous Message | Rod Taylor | 2002-06-24 12:58:13 | Re: pg_dump and ALTER TABLE / ADD FOREIGN KEY |