| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Jeff Davis <pgsql(at)j-davis(dot)com>, pgsql-hackers(at)postgresql(dot)org, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
| Subject: | Re: Distinct types |
| Date: | 2008-11-12 13:24:20 |
| Message-ID: | 491AD904.2080505@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> That's an artifact of the fact that the patch tries to piggyback on
> the DOMAIN infrastructure instead of implementing its own statement
> type etc.
This piggybacking is intentional in some way. If you read the
commentary on the SQL99 standard, distinct types were specifically
invented as a better replacement for the domains introduced in SQL92,
with the only functional difference being the casting behavior (and that
you can use distinct types as function argument types, but PostgreSQL
supports that for domains as well). So even though the names of the
object classes are different, they are really intended to be quite similar.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2008-11-12 14:08:13 | Re: Block-level CRC checks |
| Previous Message | Peter Eisentraut | 2008-11-12 13:13:57 | Re: array_length() |