Received: from shared1-mail.whowhere.com (shared1-mail.whowhere.com [209.185.123.32]) by mail.postgresql.org (8.11.1/8.11.1) with SMTP id e9VJgZl97643 for ; Tue, 31 Oct 2000 14:42:35 -0500 (EST) (envelope-from kparker@eudoramail.com) Received: from Unknown/Local ([?.?.?.?]) by shared1-mail.whowhere.com; Tue Oct 31 11:42:22 2000 To: pgsql-sql@postgresql.org Date: Tue, 31 Oct 2000 11:42:22 -0800 From: "K Parker" Message-ID: Mime-Version: 1.0 X-Sent-Mail: off Reply-To: kparker@eudoramail.com X-Expiredinmiddle: true X-Mailer: MailCity Service Subject: RE: INSERT [IGNORE] INTO TABLE X-Sender-Ip: 209.191.185.54 Organization: QUALCOMM Eudora Web-Mail (http://www.eudoramail.com:80) Content-Type: text/plain; charset=us-ascii Content-Language: en Content-Transfer-Encoding: 7bit X-Archive-Number: 200010/29 X-Sequence-Number: 29 >Not a good feature for me. Me neither, but... >Check existence and then insert or update. At least once a week I seem to be responding to this exact same suggestion. Somebody _please_ tell me if I'm the only one in the whole world who worries about race conditions? What's wrong with just making sure there's a proper unique key, and then just inserting the row? The returned error message will tell you if a failure is due to duplicate key, missing non-null column, or an actual disaster. Join 18 million Eudora users by signing up for a free Eudora Web-Mail account at http://www.eudoramail.com