| From: | chester c young <chestercyoung(at)yahoo(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: rownum |
| Date: | 2003-02-15 04:54:10 |
| Message-ID: | 20030215045410.15935.qmail@web12707.mail.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
> 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.
__________________________________________________
Do you Yahoo!?
Yahoo! Shopping - Send Flowers for Valentine's Day
http://shopping.yahoo.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | jasiek | 2003-02-15 08:45:00 | Re: sub-query optimization |
| Previous Message | Tomasz Myrta | 2003-02-15 01:52:13 | Re: sub-query optimization |