Oracle have been quick to announce new releases of mysql, but failed to issue
a notice saying uhoh, you better not use it instead, putting a small
notice, where, on a fricken manual page FFS. who the hell reads that! and
they say use version a which does not even exist, I'd hate to think
Noel,
I am really sorry for those high profile sites, which in your scenario
haven't tested their database in dev/test/stage before upgrading. Bugs happen.
Big organizations have slower communication.
Cheers,
Mihail
On Jun 30, 2012, at 0:16, Noel Butler noel.but...@ausics.net wrote:
I
Agreed - if you installed this version in production without fully testing
then it's your problem, you'll need to downgrade. If you've
tested thoroughly and hit the bug then you you're aware of the issue
already and do not have it installed in production. If you tested
thoroughly and didn't hit
Hello
I have a simple application that uses MySQL C API that works fine in
release mode, but when run in debug mode it crashes:
Unhandled exception at 0x51716970 in MSQ.exe: 0xC005: Access
violation reading location 0x.
and don't know what can be the problem.
The application was
Check the manual:
http://dev.mysql.com/doc/refman/5.5/en/news-5-5-25.html
Shawn Green
Thank you, but that warning note was not there when I first posted
this message in here. I'm not sure when the warning note appeared,
but I'd guess it was within the last 36 hours. All that I could see
was
