Repository navigation
Release v19.131.3
Summary
Chronicle starts and runs correctly when an event store has namespaces that differ only in case, for example cratis and Cratis.
Changed
- Namespace names are case-insensitive within an event store for every storage provider: where a SQL or in-memory store kept namespaces that differ only in case, the casing that holds its own data is used, the other's data stays in place, and a warning is logged (#5699)
Fixed
- Chronicle now starts when a namespace's stored name differs only in case from its existing MongoDB database: databases are opened by the casing they already have on the server (#5697)
- Removing a namespace never drops a database that another casing of the same name still uses, and case variants of the default namespace or of reserved names are rejected (#5697)
- Namespaces that differ only in case now resolve to the casing already stored for the event store, so each namespace has one set of observers and event sequences, and stored lists holding both casings are merged without losing data (#5699)