Gary V wrote:
Well the simplest fix is the one that I did not implement in the first
place, using "ON DUPLICATE KEY". However, I did not implement that
because of its only being in version 4.1 of MySQL and I still use
Debian stable for most production machines, which runs 4.0.x.
Anyway, I will poke at it some more.
- James
[OT] FYI, both 4.0 and 4.1 are available in Debian stable.
Package mysql-server
stable (misc): mysql database server binaries
4.0.24-10sarge1: alpha amd64 arm hppa i386 ia64 m68k mips mipsel powerpc
s390 sparc
4.0.24-10: amd64
Package mysql-server-4.1
stable (misc): mysql database server binaries
4.1.11a-4sarge2: alpha amd64 arm hppa i386 ia64 m68k mips mipsel powerpc
s390 sparc
4.1.11a-4: amd64
Gary V
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today - it's
FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
Thanks for pointing that out Gary. I was actually unaware of that. I
will probably change the code to use the "ON DUPLICATE KEY" because that
appears to be the best and only way I see right now.
- James
