From: | "Jeff Hoffmann" <jeff(at)remapcorp(dot)com> |
---|---|
To: | "PostgreSQL-development" <hackers(at)postgreSQL(dot)org> |
Subject: | Re: [HACKERS] What about LIMIT in SELECT ? |
Date: | 1998-10-13 19:23:35 |
Message-ID: | 005101bdf6de$f9345150$c525c4ce@go-to-jail.remapcorp.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs pgsql-hackers |
>Hi, my 2 cents...
>
>I agree completely, LIMIT would be VERY usefull in web based apps, which
>is all I run. It does not matter to me if it is not part of a formal
>standard. The idea is so common that it is a defacto standard.
i'm not familiar with mysql and using "LIMIT" but wouldn't this same effect
be achieved by declaring a cursor and fetching however many records in the
cursor? it's a very noticeable improvement when you only want the first 20
out of 500 in a 200k record database, at least.
jeff
From | Date | Subject | |
---|---|---|---|
Next Message | Eric Lee Green | 1998-10-13 20:24:20 | Re: [HACKERS] What about LIMIT in SELECT ? |
Previous Message | Oliver Elphick | 1998-06-04 03:46:44 | Re: [ADMIN] user auth & passwords |
From | Date | Subject | |
---|---|---|---|
Next Message | Marc G. Fournier | 1998-10-13 19:51:07 | Odd problem with read_pg_options ... |
Previous Message | Marc G. Fournier | 1998-10-13 19:03:48 | Re: [HACKERS] What about LIMIT in SELECT ? |