From: | Don Baccus <dhogaza(at)pacifier(dot)com> |
---|---|
To: | Taral <taral(at)taral(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] DISTINCT and ORDER BY bug? |
Date: | 2000-02-07 06:17:17 |
Message-ID: | 3.0.1.32.20000206221717.0107f4c0@mail.pacifier.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
At 12:12 AM 2/7/00 -0600, Taral wrote:
>The thing here is that random() is not deterministic on its inputs,
>whereas sin() is. Perhaps we should only allow fully deterministic ORDER
>BY? (Ugh, another flag for functions...)
Which, by it's nature is probably a misnomer, because I imagine that
PL/pgSQL functions would always have to be non deterministic whatever
their inputs? Given that unrecognized syntax is just tossed the
query executor. Thus calling any 'ole function without PL/pgSQL
really knowing what's going on?
So you probably end up with a LIST of functions by name that are built-in
and deterministic.
Or ... you simply say that results are really weird if the function has
undeterministic behavior and document it.
Tom's on the right path asking what the standard might say and what
delphic, incomprehensible answer the Oracle might have for us.
(the more I learn about the SQL standard, the more I appreciate the irony
of Oracle's corporate name!)
- Don Baccus, Portland OR <dhogaza(at)pacifier(dot)com>
Nature photos, on-line guides, Pacific Northwest
Rare Bird Alert Service and other goodies at
http://donb.photo.net.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2000-02-07 06:36:43 | Re: [HACKERS] DISTINCT and ORDER BY bug? |
Previous Message | kaiq | 2000-02-07 06:15:34 | Re: [SQL] Re: [HACKERS] Proposed Changes to PostgreSQL |