Re: PHP and PostgreSQL

From: Frank Joerdens <frank(at)joerdens(dot)de>
To: Adam Haberlach <adam(at)newsnipple(dot)com>
Cc: pgsql-php(at)postgresql(dot)org, pgsql-general(at)postgresql(dot)org
Subject: Re: PHP and PostgreSQL
Date: 2001-01-08 09:21:57
Message-ID: 3A5986B5.A71BC693@joerdens.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-php

Adam Haberlach wrote:
[ . . . ]
> Once again, this is probably all due to a difference between MySQL and Postgres.
> Judging by the MySQL code, there is a provision for the client-side libraries to
> pass tuples on to the application in the order they are sorted without necessarily
> retrieving them all to the client. AFAIK, Postgres does not do this unless you
> specifically use cursors to pull down a window of data at a time (this is correct
> behavior IMHO, your feelings may vary).

Oops, this means that I have been coding on a false assumption for quite a while now. I
guess I'll be changing quite a few while loops into for loops this week. But it's good to
have a conclusive verdict on the issue. I'd been feeling somewhat uneasy about it all
allong, what with not knowing exactly what the mechanism was . . . thanks for making this
clear!

[ . . . ]
> (and judging by the number of times I've mentioned PHP and MySQL in this
> post, it is time for this thread to go elsewhere.

I've cross-posted to php-pgsql where I think it belongs, actually.

Regards, Frank

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Pete Forman 2001-01-08 09:36:21 Re: pg_dump return status..
Previous Message hubert depesz lubaczewski 2001-01-08 08:38:50 functions returning multiple rows?

Browse pgsql-php by date

  From Date Subject
Next Message Paul Joseph McGee 2001-01-08 22:09:21 Enabling PHP
Previous Message Adam Haberlach 2001-01-08 03:47:03 Re: PHP and PostgreSQL