Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: fix README #678

Merged
merged 1 commit into from
Feb 29, 2024
Merged

docs: fix README #678

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -373,11 +373,11 @@ You may be able to alter the database to gain some readability:
ALTER DATABASE dbname SET bytea_output to 'escape';
```

## Mysql Storage options
## MySQL Storage options

### ascii field collation

The currently suggested way to create a postgres field is using `'C'` collation:
The currently suggested way to create a MySQL field is using `'utf8mb4_bin'` collation:

```ruby
t.string "ancestry", collation: 'utf8mb4_bin', null: false
Expand All @@ -402,7 +402,7 @@ t.index "ancestry"

### ascii character set

Mysql supports per column character sets. Using a character set of `ascii` will
MySQL supports per column character sets. Using a character set of `ascii` will
set this up.

```SQL
Expand Down Expand Up @@ -462,7 +462,7 @@ Model.check_ancestry_integrity!
```

It is time to run your code. Most tree methods should work fine with ancestry
and hopefully your tests only require a few minor tweaks to get up and runnnig.
and hopefully your tests only require a few minor tweaks to get up and running.

Once you are happy with how your app is running, remove the old `parent_id` column:

Expand Down