> -Original Message-
> From: Philip Hallstrom [mailto:[EMAIL PROTECTED]
>
> Because if you wanted that you'd use REPLACE which is mysql
> specific which is okay since it's mysql you're using I guess.
Except for the CRITICAL issue that REPLACE will DELETE the row first,
thereby causing al
Maybe this is some SQL standard implementation and that's why it is what it
is, but to me it seems completely retarded that you have to explicitly call
out the columns...
http://dev.mysql.com/doc/refman/5.0/en/insert-on-duplicate.html
Why doesn't it work in a more convenient and sane way?!
So i
Hello.
Perhaps you have forgotten to add col_name=expr to the end of your
query. See:
http://dev.mysql.com/doc/refman/5.0/en/insert.html
Jonathan Mangin wrote:
> I'm trying to change a couple of replace statements to
> insert...on duplicate key update (using Perl/DBI).
>
> foreach my $key (k
Hi,
It could perhaps be related to bug #8147.
http://bugs.mysql.com/bug.php?id=8147
Regards,
Jocelyn
Aleksandr Guidrevitch a écrit :
Hi all !
I'm having problem with INSERT ... ON DUPLICATE KEY UPDATE on mysql 4.1.10
--8<--8<--8<--8<--8<--8<--8<--8<--8<
INSERT
Hi!
On Oct 15, Jason McManus wrote:
> Good afternoon,
>
> I have had reason to use the new (as of 4.1.1) INSERT .. ON DUPLICATE KEY
> UPDATE syntax in MySQL. However, I am a bit confused as to the return
> value. Issuing the INSERT .. ON DUP KEY UP statement, upon finding a
> duplicate key and
Hi,
ON DUPLICATE KEY UPDATE is only available with MySQL 4.1.x.
Regards,
Jocelyn
- Original Message -
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, July 08, 2003 8:32 AM
Subject: Insert...on duplicate key update
> >Description:
> I have been writing an update progr
