The information on this page is included into other pages. When updating this page, add your content between the \{excerpt} tags if you want it to be included in other pages too.

'Collation' refers to a set of rules that determine how data is sorted and compared. Case sensitivity is one aspect of collation. Other aspects include sensitivity to kana (Japanese script) and to width (single- versus double-byte characters).

Case-sensitive or case-insensitive collation — how should you create your Confluence database? What about when you are migrating your existing Confluence instance from one database to another?

新しい Confluence インスタンスの設定

For new Confluence instances, we recommend case-insensitive collation because it helps enforce uniqueness constraints that make sense in our applications. That is, if you don't want to allow 'joebloggs', 'joeBloggs', 'JoeBloggs', etc. as different valid usernames, you should use case-insensitive collation.

別のデータベースへの既存の Confluence インスタンスの移行

The default Confluence Standalone configuration uses a case-sensitive database. If you are migrating from this configuration to a new database, you may have existing usernames with 'joebloggs', 'joeBloggs', 'JoeBloggs', etc. In this case, if your new database is case-insensitive, your XML import will fail unless you clean up the data first. That's why we recommend sticking with case sensitivity if you're migrating databases.