You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I do think it makes sense to use C.UTF-8 as it does not depend on OS locale settings and hence is deterministic across Postgres instances.
With en_US.UTF-8 any updates to glibc or ICU could affect the existing sorting order. If it is really needed, it can still be defined on column level.
Copy file name to clipboardExpand all lines: ruby_on_rails/app_initialisation.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,6 +40,10 @@ Some other adjustments must be performed manually.
40
40
41
41
### Automatic adjustments
42
42
43
+
> ⭐️The `config/database.yml` is updated to have a `collation: C.UTF-8` setting.
44
+
> This ensures deterministic, locale-independent sorting and avoids inconsistencies between local and production
45
+
> environments.
46
+
43
47
> ⭐The Gemfile reads the required ruby version from the `.ruby-version` file.
44
48
> [This is used by Heroku to determine what version to use.](https://devcenter.heroku.com/articles/ruby-versions)
45
49
> Deploio reads the ruby version from the Gemfile, with the .ruby-version file inlined into it. https://paketo.io/docs/howto/ruby/#override-the-detected-ruby-version
0 commit comments