comment on

http://www.mysql.com/doc/en/INSERT.html tells you the use for ON DUPLICATE KEY UPDATE, so you may want to check that out.

I'd be interested to hear more details about the situation which you are stuck in, as I'd like to see an example of where you'd want to use this feature. Myself, I use primary keys because of the fact that they normally must be unique. I have yet to come across a case where refusing to add data to the table because of an existing primary key value is a bad idea.

I hope you post more info so that I can understand your position. ON DUPLICATE KEY UPDATE acts differently depending on how the table is set up (ie: if more than one column is marked as unique). The link at the beginning of the post vaguely mentions this fact.

In reply to Re: MySQL and Duplicate Keys by Coruscate
in thread MySQL and Duplicate Keys by cidaris

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Your skill will accomplish what the force of many cannot
	PerlMonks