| From: | "Thomas G(dot) Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu> |
|---|---|
| To: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | jwieck(at)debis(dot)com, eric(at)linux-hw(dot)com, jeff(at)remapcorp(dot)com, hackers(at)postgreSQL(dot)org |
| Subject: | Re: [HACKERS] What about LIMIT in SELECT ? |
| Date: | 1998-10-16 06:52:31 |
| Message-ID: | 3626ED2F.A0247B01@alumni.caltech.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-hackers |
> Your solution really is tailored for this 'partial' query application,
> and I think it is a big need for certain applications that can't use
> cursors, like web apps. Most other apps have long-time connections to
> the database, and are better off with cursors.
And there are persistant web servers available too, to help work around
this "stateless connection problem"? Let's remember that we are solving
a problem which has few requirements for data integrity, and which is
starting to get out of the realm of Postgres' strengths (almost any
scheme can barf data up to a client if it doesn't care whether it is
repeatable or complete).
Neat stuff though :)
- Tom
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hiroshi Inoue | 1998-10-20 08:24:09 | RE: [HACKERS] What about LIMIT in SELECT ? |
| Previous Message | Bruce Momjian | 1998-10-16 05:34:33 | Re: [HACKERS] What about LIMIT in SELECT ? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Edmund Mergl | 1998-10-16 10:40:55 | Re: [HACKERS] perl interface bug? |
| Previous Message | Thomas G. Lockhart | 1998-10-16 06:32:40 | Re: [HACKERS] What about LIMIT in SELECT ? |