Re: [HACKERS] Oid Questions

From: Zeev Suraski <bourbon(at)netvision(dot)net(dot)il>
To: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
Cc: mrogan(at)fpelectronics(dot)com, hackers(at)postgreSQL(dot)org, php-dev(at)php(dot)iquest(dot)net
Subject: Re: [HACKERS] Oid Questions
Date: 1998-01-23 00:33:09
Message-ID: 3.0.3.32.19980123003309.00cffd50@bourbon.netvision.net.il
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I'll try to rephrase the question without taking 3 complex paragraphs to do
that :)

Is there a way to know a PostgresSQL result holds NO interesting
information (no rows, no oids, no nothing)?

The more I think of it, the more it seems like this isn't the case with
PostgresSQL. Moreover, it seems like in most cases the result holds one
interesting tidbit of information or another. When I wrote the MySQL
module, basically, I made any query that did not return rows (not including
select's that returned 0 rows) but succeeded return TRUE instead of a
result handler, since there wasn't much point at keeping that result. With
MySQL the information about the last inserted id (mysql_insert_it(), I
think it's comparable to the last oid in pgsql) and the number of affected
rows can be obtained from the 'server' structure, and not the restul
structure as it is with Postgres.

I guess I'll change the Postgres module to always keep the result
structures and return result identifiers on a successful query.

Zeev
---
Zeev Suraski <zeev(at)php(dot)net>
Web programmer, System administrator, Netvision LTD
http://bourbon.netvision.net.il/ ICQ: 1450980
For a PGP public key, finger bourbon(at)netvision(dot)net(dot)il

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Joseph Heil 1998-01-23 03:46:17 Re: [PORTS] Important Announcement
Previous Message Bruce Momjian 1998-01-23 00:09:05 LOCK command