Received: from davinci.ethosmedia.com (davinci.ethosmedia.com [209.10.40.250]) by postgresql.org (8.11.3/8.11.4) with ESMTP id f9HFpiP57093 for ; Wed, 17 Oct 2001 11:51:45 -0400 (EDT) (envelope-from josh@agliodbs.com) Received: from [209.10.40.250] (account ) by davinci.ethosmedia.com (CommuniGate Pro WebUser 3.4.1) with HTTP id 149645; Wed, 17 Oct 2001 08:51:39 -0700 From: "Josh Berkus" Subject: Re: last OID and connections? To: johnny@halfahead.dk, pgsql-php@postgresql.org X-Mailer: CommuniGate Pro Web Mailer v.3.4.1 Date: Wed, 17 Oct 2001 08:51:39 -0700 Message-ID: In-Reply-To: <200110171527170784.01357C60@mail.halfahead.dk> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="_===149645====davinci.ethosmedia.com===_" X-Archive-Number: 200110/74 X-Sequence-Number: 627 This is a multi-part MIME message --_===149645====davinci.ethosmedia.com===_ Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit Johnny, > Once I get a current project to production state, I'm going to get a > heap of users performing updates simultaneously through the same > update.php, and that raises a few questions: > > 1. will pg_getlastoid() return the last oid inserted *by this user*, > *on this page*, *on this connection*, or is there a possibility for > them to get mixed up, because the database gets a connection from the > same user (php), and reuses connections or something? Use a more sophisticated scheme. I understand that the current OID scheme is eventually being phased out of future Postgres releases (with backwards compatibility, of course!) and replaced with something else because of problems with very large/very old databases. Or so the rumor mill goes. I handle this issue by wrapping all adds and edits in functions; each function returns the primary key of the record as its result. NEXTVAL and CURVAL are your friends! > 2. I find oid's pretty clever, but are they good for unique keys? It > seems, foreign key constraints won't use oid's in the current > release, should i use serials instead? Yes, you should use SERIALs instead. OIDs are for system use only, and will cause problems with backup/restore as well as databases with more than 2 billion objects. -Josh ______AGLIO DATABASE SOLUTIONS___________________________ Josh Berkus Complete information technology josh@agliodbs.com and data management solutions (415) 565-7293 for law firms, small businesses fax 621-2533 and non-profit organizations. San Francisco --_===149645====davinci.ethosmedia.com===_ Content-Type: text/plain Content-Disposition: attachment; filename="" Content-Transfer-Encoding: base64 DQo= --_===149645====davinci.ethosmedia.com===_ Content-Type: text/plain Content-Disposition: attachment; filename="" Content-Transfer-Encoding: base64 DQo= --_===149645====davinci.ethosmedia.com===_ Content-Type: text/plain Content-Disposition: attachment; filename="" Content-Transfer-Encoding: base64 DQo= --_===149645====davinci.ethosmedia.com===_--