-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tom Lane wrote:
| Gaetano Mendola <[EMAIL PROTECTED]> writes:
|
|>my warning was due the fact that in the docs is written nowhere this
|>drawback.
|
|
| The SELECT reference page already says that the output rows are computed
| before applying ORDER BY
Gaetano Mendola <[EMAIL PROTECTED]> writes:
> my warning was due the fact that in the docs is written nowhere this
> drawback.
The SELECT reference page already says that the output rows are computed
before applying ORDER BY or DISTINCT.
regards, tom lane
Greg Stark wrote:
Gaetano Mendola <[EMAIL PROTECTED]> writes:
now what do I see is that for each different x value
the foo is executed more than once, I guess this is because
the distinct filter out the rows after executing the query.
Is this behaviour the normal one? Shall be not documented ?
Us
Gaetano Mendola <[EMAIL PROTECTED]> writes:
> now what do I see is that for each different x value
> the foo is executed more than once, I guess this is because
> the distinct filter out the rows after executing the query.
>
> Is this behaviour the normal one? Shall be not documented ?
Usually
Hi all,
I have a query that is something like this:
SELECT DISTINCT ON ( x ) x, foo(x)
FROM ...
now what do I see is that for each different x value
the foo is executed more than once, I guess this is because
the distinct filter out the rows after executing the query.
Is this behaviour the normal o
