Hal Vaughan [EMAIL PROTECTED] wrote on 24/08/2005 17:41:36:
#
Okay, so INSERT IGNORE only works if I am avoiding duplicate keys. Is
there
any way to use INSERT the way I thought INSERT IGNORE worked -- in other
words is there any keyword for the INSERT command to keep it from
On Thursday 25 August 2005 04:44 am, [EMAIL PROTECTED] wrote:
Hal Vaughan [EMAIL PROTECTED] wrote on 24/08/2005 17:41:36:
#
Okay, so INSERT IGNORE only works if I am avoiding duplicate keys. Is
there
any way to use INSERT the way I thought INSERT IGNORE worked -- in other
words is
Hal,
*IF* INSERT IGNORE worked ...
INSERT IGNORE _does_ work exactly as documented in the manual: "If you
specify the IGNORE keyword in an INSERT statement, errors that occur while
executing the statement are treated as warnings instead. For example,
without IGNORE, a row that duplicates an
Hi Hal,
in order to get INSERT IGNORE to work as you want it you must violate
a unique index somehow, i.e. you must have a unique index on Name,Value
or both and then you would get a quiet ignore of that violation.
The IGNORE keyword doesn't make the INSERT as such different, it just
affects the
The insert will only be bounced where you specify the columns as unique.
Thus you need either separate UNIQUE indexes on Name and Value, if you
want them to be individually unique, or a single joint UNIQUE index if you
want them to be jointly unique but separately duplicable. The INSERT
On Wednesday 24 August 2005 02:47 am, Hal Vaughan wrote:
I may have a misunderstanding of this, but as I have been told, if I have a
table with 3 columns, Idx (an Index column, unique, auto-increment), Name,
Value (both varchar), and I try a command like this:
INSERT IGNORE INTO myTable SET
Hal Vaughan [EMAIL PROTECTED] wrote on 08/24/2005 12:41:36 PM:
On Wednesday 24 August 2005 02:47 am, Hal Vaughan wrote:
I may have a misunderstanding of this, but as I have been told, if I
have a
table with 3 columns, Idx (an Index column, unique, auto-increment),
Name,
Value (both
