Summary: | Querying GRANT on a VIEW in MySQL-5.0.19 causes crash | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Matt Brooks <mbrooks> |
Component: | [OLD] Server | Assignee: | Gentoo Linux MySQL bugs team <mysql-bugs> |
Status: | RESOLVED CANTFIX | ||
Severity: | critical | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Matt Brooks
2006-03-18 01:08:01 UTC
*** Bug 126636 has been marked as a duplicate of this bug. *** query SQL: USE mydns;# MySQL ha restituito un insieme vuoto (i.e. zero righe). GRANT SELECT ON rr TO gentoouser;# MySQL ha restituito un insieme vuoto (i.e. zero righe). ==> works for me emerge -pv mysql [ebuild R ] dev-db/mysql-5.0.19 USE="berkdb cluster extraengine max-idx-128 perl ssl -big-tables -debug -embedded -minimal -srvdir -static" Need at least emerge -pv mysql, since we do not apply significant patches to "C" code, you can try to build MySQL from the source, using the configure options you could see during emerge phase (or in /var/tmp/portage/mysql-5.0.19/work/mysql/config.log) If you chose to build from sources read the MySQL docs signaled during the crash. Mysql GRANT crash only happens on an upgrade from mysql 4.0 to mysql 5.0. The user needs to run the following commands to fix this: mysqlcheck --check-upgrade --all-databases --auto-repair mysql_fix_privilege_tables I don't know if this can be included in the ebuild or what, but I feel the user at least needs to be notified. (In reply to comment #3) > Mysql GRANT crash only happens on an upgrade from mysql 4.0 to mysql 5.0. Yuck?! The databases are not compatible even between 4.0 and 4.1 (http://www.gentoo.org/doc/en/mysql-upgrading.xml), how did you suppose that it'll straight work when upgraded from 4.0 to 5.0? It was actually an upgrade from 4.0 to 4.1 to 5.0. The mentioned query works correctly and it's not supported to do a straight 4.0 --> 5.0 upgrade, or any else major version upgrade in mysql, without at least executing the various update scripts (mysql_fix_privileges in this case). Closing this bug, best regards, CHTEKK. |