From: | "Robby Slaughter" <webmaster(at)robbyslaughter(dot)com> |
---|---|
To: | "Josh Berkus" <josh(at)agliodbs(dot)com>, "Peter Eisentraut" <peter_e(at)gmx(dot)net> |
Cc: | <pgsql-sql(at)postgresql(dot)org> |
Subject: | RE: Hey! ORDER BY in VIEWS? |
Date: | 2001-07-15 20:02:43 |
Message-ID: | EPEHLKLEHAHLONFOKNHNAENBDCAA.webmaster@robbyslaughter.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
Josh:
You wondered:
>What happens if I put an ORDER BY in a view, then call an ORDER BY in a
>query, e.g.:
>
>CREATE VIEW test_view AS
>SELECT client_name, city, zip FROM clients
>WHERE zip IS NOT NULL
>ORDER BY zip;
>
>SELECT * FROM test_view ORDER BY city;
>
>Does the second ORDER BY override or suppliment the view ORDER BY, or is
>it ignored?
I think this question falls into the "Don't ask, don't tell"
category of computer related questions. I can't think of a reason
to design this way, the behavior isn't specified or sensible, so just
don't do it!
Sorry if I'm over-admonishing. Curiosity killed the cat.
-Robby
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Huxton | 2001-07-15 20:58:22 | ANNOUNCE: Updated PostgreSQL Notes |
Previous Message | Josh Berkus | 2001-07-15 19:41:15 | Re: Hey! ORDER BY in VIEWS? |