Re: [GENERAL] Practical Cursors

2001-10-16 Thread Christopher Masto
On Tue, Sep 25, 2001 at 12:06:48AM -0400, Micah Yoder wrote: > (sorry to reply to a week-old message. need to keep up with this list more!) Ditto, but more so. > I then wrote a daemon in C to do the work and store the results in RAM. The > PHP script connected to the daemon via a socket, and

Re: [GENERAL] Practical Cursors

2001-09-25 Thread Jan Wieck
Micah Yoder wrote: > (sorry to reply to a week-old message. need to keep up with this list more!) > > On Monday 17 September 2001 17:04, you wrote: > > > There is an obvious benefit to the use of cursors within a persistent > > environment. In other words, if my connection to the database is live

Re: [GENERAL] Practical Cursors

2001-09-25 Thread Micah Yoder
(sorry to reply to a week-old message. need to keep up with this list more!) On Monday 17 September 2001 17:04, you wrote: > There is an obvious benefit to the use of cursors within a persistent > environment. In other words, if my connection to the database is live, I > can increase my query a

Re: [GENERAL] Practical Cursors

2001-09-18 Thread Sam Tregar
On Mon, 17 Sep 2001, Command Prompt, Inc. wrote: > Is this truly the case, or is there a way for PostgreSQL to remember the > connection identifier so that the next time a PHP connection is made with > the same identifier a transaction can be completed? Anything is possible - you could write a s

Re: [GENERAL] Practical Cursors

2001-09-17 Thread Alex Pilosov
On Mon, 17 Sep 2001, Command Prompt, Inc. wrote: > However, using something like PHP will not allow this because HTTP is > stateless and PostgreSQL will not know from one transaction to the next > that the results of the connection are related. > > Is this truly the case, or is there a way for P