| From: | "Matthew N(dot) Dodd" <winter(at)jurai(dot)net> |
|---|---|
| To: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | "Marc G(dot) Fournier" <scrappy(at)hub(dot)org>, 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-14 06:25:31 |
| Message-ID: | Pine.BSF.4.02.9810140221520.17054-100000@sasami.jurai.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-hackers |
On Tue, 13 Oct 1998, Bruce Momjian wrote:
> My guess in a web application is that the transaction is started for
> every new page, so you can't have transactions spanning SQL sessions.
>
> LIMIT theoretically would allow you to start up where you left off.
It really does depend largly on the architecuture of the website doesn't
it.
LIMIT probably allows web site developers a quick and dirty way to do what
should properly be done with a web-DB proxy. I seem to remember mod_perl
having a solution for this sort of thing.
--
| Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS |
| winter(at)jurai(dot)net | This Space For Rent | ix86,sparc,m68k,pmax,vax |
| http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matthew N. Dodd | 1998-10-14 06:32:30 | Re: [HACKERS] What about LIMIT in SELECT ? |
| Previous Message | Bruce Momjian | 1998-10-14 00:47:01 | Re: [HACKERS] What about LIMIT in SELECT ? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matthew N. Dodd | 1998-10-14 06:32:30 | Re: [HACKERS] What about LIMIT in SELECT ? |
| Previous Message | Thomas G. Lockhart | 1998-10-14 06:19:11 | Re: [HACKERS] Alternative to LIMIT in SELECT ? |