Skip to content

Conversation

@Blargian
Copy link
Member

Summary

Regarding https://clickhouse-inc.slack.com/archives/C03A9B0H05T/p1755032139630649, this PR updates the instructions for MySQL connection to recommend creating a readonly user with how to do so. Also improves the formatting of this snippet.

Checklist

@Blargian Blargian requested a review from a team as a code owner August 13, 2025 08:45
@vercel
Copy link

vercel bot commented Aug 13, 2025

@Blargian is attempting to deploy a commit to the ClickHouse Team on Vercel.

A member of the Team first needs to authorize it.

@vercel
Copy link

vercel bot commented Aug 13, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Project Deployment Preview Updated (UTC)
clickhouse-docs Ready Preview Aug 13, 2025 8:57am

@Blargian Blargian requested a review from mshustov August 13, 2025 08:47
@Blargian
Copy link
Member Author

@mshustov could I please ask for your review on this one? As I understood it, we should use the readonly setting, in addition to granting only SELECT to the needed databases and tables?

CREATE USER mysql4foobar_team1 IDENTIFIED WITH double_sha1_password BY 'YourPassword42$';
```
```sql
CREATE SETTINGS PROFILE readonly_profile SETTINGS readonly = 1
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure whether we need readonly = 1 (strict mode) or readonly = 2 (allow changing some settings https://clickhouse.com/docs/operations/settings/permissions-for-queries#readonly)

@Blargian Blargian merged commit d3c91e1 into ClickHouse:main Aug 14, 2025
10 of 13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants