From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | Terry <td3201(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: select issue with order v8.1 |
Date: | 2010-02-25 04:30:55 |
Message-ID: | dcc563d11002242030t799eb035x30d1cce9f434774@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, Feb 24, 2010 at 8:50 PM, Terry <td3201(at)gmail(dot)com> wrote:
> Hello,
>
> I have an application that is doing something stupid in that it is
> tacking on its own order clause at the end of the statement I am
> providing.
>
> For example, I am putting this statement in:
> select ev_id,type,ev_time,category,error,ev_text,userid,ex_long,client_ex_long,ex_text
> from clients_event_log limit 100
>
> It is tacking on ORDER BY ev_id. The problem is that isn't per the
> syntax. Can anyone think of anything clever to get around this stupid
> application doing what it is doing? For example, anything I can do
> beside limit?
>
> I appreciate the thoughts!
You could either wrap it in a subselect or make a view.
select * from (select
ev_id,type,ev_time,category,error,ev_text,userid,ex_long,client_ex_long,ex_text
from clients_event_log limit 100) as a
and an order by tacked on the end of that is ok.
From | Date | Subject | |
---|---|---|---|
Next Message | Martijn van Oosterhout | 2010-02-25 08:11:54 | Re: Performance comparison |
Previous Message | Tom Lane | 2010-02-25 04:07:28 | Re: select issue with order v8.1 |