Activity overview
Latest activity by JamesC2
I did investigate upgrading MySQL, but it's quite a big job, so after a couple of attempts in a VM snapshot, decided not to go further at the moment, so can't confirm whether that would fix it - we're probably both assuming it would. / comments
I did investigate upgrading MySQL, but it's quite a big job, so after a couple of attempts in a VM snapshot, decided not to go further at the moment, so can't confirm whether that would fix it - we...
Sorry, I should have thought of providing that info.
I'm on 5.0.77, on CentOS 5.5 (and 5.7 on a dev box).
I'll try to upgrade MySQL, at least on one box, and see if that helps. I'd say it's perfectly reasonable not to support older versions, but given that 5.0.77 is the latest package available in CentOS/RHEL 5 standard repository, there may be plenty others out there stuck in the past like us! / comments
Sorry, I should have thought of providing that info.
I'm on 5.0.77, on CentOS 5.5 (and 5.7 on a dev box).
I'll try to upgrade MySQL, at least on one box, and see if that helps. I'd say it's perfect...
Thanks for such a quick reply.
Sadly, I was on the latest version (1.0.0.292), and am still finding this bug. Let me know if I can provide any more details to help. / comments
Thanks for such a quick reply.
Sadly, I was on the latest version (1.0.0.292), and am still finding this bug. Let me know if I can provide any more details to help.
Timestamp fields with ON UPDATE set don't compare properly
MySQL is awkward in how it handles timestamps, but I seem to come across an unfortunate (and repeatable) problem. In summary, MySQL COmpare never seems to include an "ON UPDATE" clause in its table...