* Robert McGinnis <fprefect@elite.net> [010130 07:45] wrote:
> On Mon, 29 Jan 2001, Alfred Perlstein wrote:
>
> > I'm not sure if this is true, but I think php doesn't support
> > cursors, so large queiries may have to be sucked into the
> > webserver instead of processed one row at a time.
> >
> >
> I have used cursors with php for over a year. The problem is that is does
> not support them natively; any code that tests the call for pg_exec may
> fail since the return is undefined. Here's how I write the code:
> //Note this is off the top of my head, you code may vary :-)
>
[snip]
>
> Move forward and backward works as before the fetch. The part that I
> don't like is the inability to check whether the transaction block querys
> work; I had to console myself with counting the number of results I should
> get for the same query. The bad part is that there is WAY to many queries
> being executed; the good part is it save a great many lines of
> quasi-convoluted logic whilst incrementing to the n or n+1 row of an
> answer. I hope this helps,
It's nice but not as nice as having true support so that one doesn't need
to do all those redundant checks and queries.
--
-Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org]
"I have the heart of a child; I keep it in a jar on my desk."