I run MySQL 5.6 on OS 10.11. There is a table that appears to be corrupt: it
does not respond to queries, and the command to drop it does not execute. The
database seems to be OK in other respects. What can I do to get rid of the
table? Would it be safe just to remove the two .frm and .ibd
Am 02.07.2016 um 16:49 schrieb Martin Mueller:
I run MySQL 5.6 on OS 10.11. There is a table that appears to be corrupt: it
does not respond to queries, and the command to drop it does not execute. The
database seems to be OK in other respects. What can I do to get rid of the
table? Would
2016/07/02 18:49 ... Martin Mueller:
It’s clear from Section 6.6 of the Reference manual that I need to make sure
that the new installation differs from the old one with regard to the data
directory, the port number, the socket, the shared memory-base-name, and the
pid-file.
It’s less clear
Thanks. That’s helpful and makes me think that there may be a “Mac hole” in the
MySQL documentation. Windows is one thing and Linux another. OS X is sort of
Unix, but only sort of, and the conventions are not as firmly established. For
instance, the instructions for the MySQl Sandbox—on the
Dear Mr. Green,
After struggling for several hours with installing an alternate installation of
MySQL, I’ve concluded that this may be beyond my feeble powers but also that
the official instructions are not very good. They are written for system
administrators who are doing work of this kind
Am 03.07.2016 um 00:49 schrieb Martin Mueller:
After struggling for several hours with installing an alternate installation of
MySQL, I’ve concluded that this may be beyond my feeble powers but also that
the official instructions are not very good. They are written for system
administrators
Am 03.07.2016 um 04:47 schrieb Martin Mueller:
If port 3306 is taken, how is one supposed to know that 3307 is a good
alternative? Why not 3317 or 3703
seriously?
when this is your point about bad documentation than you just don't have
a point - there is no "good alternive". ist's only a
