Groups | Search | Server Info | Login | Register
Groups > comp.databases.mysql > #7630
| From | pinnerite <pinnerite@gmail.com> |
|---|---|
| Newsgroups | comp.databases.mysql |
| Subject | Re: Cannot remove MySQL completely |
| Date | 2022-01-17 16:57 +0000 |
| Organization | A noiseless patient Spider |
| Message-ID | <20220117165750.f8dc48ba66e8fc7513db85f0@gmail.com> (permalink) |
| References | <20220117114805.c031fa47fced17cde62197b8@gmail.com> <4789f309-afb4-6231-cadc-2d1a524eee3a@gmx.de> |
On Mon, 17 Jan 2022 15:03:46 +0100 Axel Schwenke <axel.schwenke@gmx.de> wrote: > On 17.01.2022 12:48, pinnerite wrote: > > Recent posts have culminated in my not being able to remedy a corruption in the user table. > > > > I decided to remove MySQL and reinstall. > > This is not Windows. Your cannot solve problems by reinstalling software. Or > rebooting your computer. > > > When I reinstalled, the corrupt user table was still there. > > Because the data directory is not auto-removed. This is for safety. A fresh > datadir is only created if none exists. > > Now: what "corruption" do you have in the `user` table? Keep in mind that > you should not operate on the user table with UPDATE and DELETE statements. > There are dedicated CREATE user and DROP user statements. Read the manual on > "Access Control and Account Management" Thank you. Slightly too late - this time. I have completely restored MySQL. The corupt data is gone. At the moment I can only get int MySQL from a root prompt. Otherwise it asks for the root password which I have not set(?). -- Mint 20.3, kernel 5.4.0-95-generic, Cinnamon 5.2.7 running on an AMD Phenom II X4 Black edition processor with 16GB of DRAM.
Back to comp.databases.mysql | Previous | Next — Previous in thread | Next in thread | Find similar
Cannot remove MySQL completely pinnerite <pinnerite@gmail.com> - 2022-01-17 11:48 +0000
Re: Cannot remove MySQL completely Bit Twister <BitTwister@mouse-potato.com> - 2022-01-17 06:26 -0600
Re: Cannot remove MySQL completely The Natural Philosopher <tnp@invalid.invalid> - 2022-01-17 13:22 +0000
Re: Cannot remove MySQL completely Axel Schwenke <axel.schwenke@gmx.de> - 2022-01-17 15:03 +0100
Re: Cannot remove MySQL completely pinnerite <pinnerite@gmail.com> - 2022-01-17 16:57 +0000
Re: Cannot remove MySQL completely Axel Schwenke <axel.schwenke@gmx.de> - 2022-01-18 10:44 +0100
Re: Cannot remove MySQL completely pinnerite <pinnerite@gmail.com> - 2022-01-18 12:48 +0000
Re: Cannot remove MySQL completely Axel Schwenke <axel.schwenke@gmx.de> - 2022-01-18 15:26 +0100
Re: Cannot remove MySQL completely pinnerite <pinnerite@gmail.com> - 2022-01-18 16:40 +0000
Re: Cannot remove MySQL completely Axel Schwenke <axel.schwenke@gmx.de> - 2022-01-19 17:43 +0100
Re: Cannot remove MySQL completely pinnerite <pinnerite@gmail.com> - 2022-01-20 12:44 +0000
Re: Cannot remove MySQL completely Axel Schwenke <axel.schwenke@gmx.de> - 2022-01-20 16:50 +0100
Re: Cannot remove MySQL completely Jerry Stuckle <jstucklex@attglobal.net> - 2022-01-18 15:49 -0500
Re: Cannot remove MySQL completely Dr Eberhard Lisse <nospam@lisse.NA> - 2022-01-19 12:29 +0200
Re: Cannot remove MySQL completely Jerry Stuckle <jstucklex@attglobal.net> - 2022-01-19 17:15 -0500
Re: Cannot remove MySQL completely Dr Eberhard Lisse <nospam@lisse.NA> - 2022-01-20 15:30 +0200
Re: Cannot remove MySQL completely Jerry Stuckle <jstucklex@attglobal.net> - 2022-01-20 13:06 -0500
csiph-web