| From: | Terry Yapt <pgsql(at)technovell(dot)com> |
|---|---|
| To: | pgsql-sql(at)postgresql(dot)org |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: rownum |
| Date: | 2003-02-17 16:25:40 |
| Message-ID: | 3E510D04.5EEC1808@technovell.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
Perhaps you are using ROWNUM like LIMIT/OFFSET...
http://www.postgresql.org/docs/view.php?version=7.3&idoc=1&file=queries-limit.html
I hope this helps...
chester c young wrote:
>
> > Considering that it can trivially be done on the client side, I think
> > it would be a hard sell to put such a wart into the protocol ...
>
> having used Oracle for many years, I cannot think of a project in which
> I did not use rownum, including within procedures and triggers and
> subqueries. can usually be easily done - loop within loop - but more
> easily and bugfree as column within select.
>
> by "wart" do you mean aesthetically or code-wise? naively, it seems
> like pg is already keeping a row counter to implement limit.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Brad Hilton | 2003-02-17 17:20:07 | Re: sub-query optimization |
| Previous Message | iafmgc | 2003-02-17 14:32:07 |