Re: DB and INSERT's allready exists?

From: Date: Wed, 13 Jul 2005 10:58:37 +0000
Subject: Re: DB and INSERT's allready exists?
References: 1 2  Groups: php.pear.general 
Request: Send a blank email to pear-general+get-19965@lists.php.net to get a copy of this message
Am Mittwoch, den 13.07.2005, 11:53 +0200 schrieb Klaus Guenther: > The easy way is... first do a SELECT to see if there is a match before > trying to insert. > > I assume you're using DB? Then you might also be able to check for the > error on insert and look at the error code and based on the error do > what you want. However, trying to insert bad info into the database > isn't very wise, imho. I'd anyway first do the select :) But why? I thought thats what INSERT is for, otherwise we would not need INSERT and REPLACE, one of it would be enaugh. So I think I use INSERT and catch the error. Doing a select before inserting would make more queries, and I think it would slow down the process of my script. Thanks, Martin > hth, > Klaus > > On 7/13/2005 10:10 AM, Martin Klaffenboeck spake the following words: > > >Hello! > > > >I'm using an insert statement to register new users. Now I set a mysql > >'Email' field unique so that an user cannot register twice. > > > >But how can I check if the INSERT failed because of an unique? I want > >to tell the user he's allready registerd and ask to send a new password. > > > >How can I do that? > > > >thanks, > >Martin > > > > > > >

« previous php.pear.general (#19965) next »