Comment 2 for bug 1800189

Mr. Basak:

The information you share is enlightening. I had no idea that "sudo
mysql" would (by itself)
access the installed service.

I agree. We should add instruction on how to set up a user account so
that the user does not
wrongly infer that root access should be used as a standard practice.

Do you believe that (1) the length of the content in such a new section,
and (2) the fact that
advanced users may want to skip over the section unless necessary,
should warrant the content
being placed on a separate page with a link to "additional information"
placed in the current
installation page?

Or, do you feel that it would be better placed on the page with the
installation and setup instructions?

I'd be willing to help draft the instructions for review by someone more
knowledgeable such as yourself.

Let me know how I can help and whether a separate page should be created
or if content should
be added to the current page.

Kind regards,

Jared Clemence

On 10/29/18 6:46 AM, Robie Basak wrote:
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better.
>
> It's a reasonable point that the guide doesn't currently cover how users
> can connect an SQL monitor to the default installed MySQL server
> package, and I welcome the addition you suggest, with one minor
> modification: "sudo mysql" is all that is required; "-u root" and "-p"
> are unnecessary.
>
> It's not that the user must use a blank password. It's that no password
> is required when the user is running the client as Unix root because the
> server is able to detect that and doesn't require a password prompt to
> authenticate in that case. This is why there is no default password set
> by default now. And "root" is the default since the sudo means that the
> mysql client is running as root.
>
> If we add this section, it might be wise to also add a section
> explaining how to create a database and a user to access this database -
> so that users don't get misled into thinking that regular database
> access should be done via "sudo". I wonder whether we should add the
> "Accessing" part without also adding this "Setting up manually for
> regular use" part to ensure this.
>