Today a customer had a strange problem with some VirtueMart prices. Since the problem didn't occur on the development server, I compared the two databases using Toad for MySQL 7.9.0.637 (32-bit) and, after switching to the new version, Toad for MySQL 8.0.0.290 (64-bit). In both cases I couldn't find any significant differences that could cause the issue (of course I had already checked the files, too). I needed quite some time to realize that the affected products had start and and dates set for their prices, probably caused by some weird VirtueMart bug. Their datetime values were all set to '0001-01-01 00:00:00' instead of '0000-00-00 00:00:00', which stands for 'no date set'. The values were correct in the development site's database, yet Toad showed them as '0001-01-01 00:00:00', too, probably because of some date conversion. So although the fields had different values, they were shown as identical. This is suboptimal, to say the least... It would be great if Toad showed the correct values instead of trying to interpret them in some way.
↧