From 58a05098bccbd4be24bee239cd6eb36c8af4d6eb Mon Sep 17 00:00:00 2001 From: Paula Date: Wed, 11 Oct 2023 14:13:36 +0200 Subject: [PATCH 1/2] --database.extended-names enabled by default --- .../incompatible-changes-in-3-12.md | 19 ++++++++++++++++++- .../version-3.12/whats-new-in-3-12.md | 19 +++++++++++++++++++ 2 files changed, 37 insertions(+), 1 deletion(-) diff --git a/site/content/3.12/release-notes/version-3.12/incompatible-changes-in-3-12.md b/site/content/3.12/release-notes/version-3.12/incompatible-changes-in-3-12.md index 3ef151d7f1..c872924e69 100644 --- a/site/content/3.12/release-notes/version-3.12/incompatible-changes-in-3-12.md +++ b/site/content/3.12/release-notes/version-3.12/incompatible-changes-in-3-12.md @@ -172,7 +172,24 @@ the JavaScript graph modules. ## Startup options - +### `--database.extended-names` enabled by default + +The `--database.extended-names` startup option is now enabled by default. +This allows you to use Unicode characters inside database names, collection names, +view names and index names by default, unless you explicitly turn off the +functionality. + +Note that once a server in your deployment has been started with the flag set to +`true`, it stores this setting permanently. Switching the startup option back to +`false` raises a warning about the option change at startup, but it is not +blockig the startup. + +Existing databases, collections, views and indexes with extended names can still +be used even with the option set back to `false`, but no new database objects +with extended names can be created with the option disabled. This state is only +meant to facilitate downgrading or reverting the option change. When the option +is set to `false`, all database objects with extended names that were created +in the meantime should be removed manually. ## Client tools diff --git a/site/content/3.12/release-notes/version-3.12/whats-new-in-3-12.md b/site/content/3.12/release-notes/version-3.12/whats-new-in-3-12.md index b9f604ceaa..2ffe9b6334 100644 --- a/site/content/3.12/release-notes/version-3.12/whats-new-in-3-12.md +++ b/site/content/3.12/release-notes/version-3.12/whats-new-in-3-12.md @@ -125,6 +125,25 @@ attempt to create an additional database fails with error if other databases are dropped first. The default value for this option is unlimited, so an arbitrary amount of databases can be created. +### `--database.extended-names` enabled by default + +The `--database.extended-names` startup option is now enabled by default. +This allows you to use Unicode characters inside database names, collection names, +view names and index names by default, unless you explicitly turn off the +functionality. + +Note that once a server in your deployment has been started with the flag set to +`true`, it stores this setting permanently. Switching the startup option back to +`false` raises a warning about the option change at startup, but it is not +blockig the startup. + +Existing databases, collections, views and indexes with extended names can still +be used even with the option set back to `false`, but no new database objects +with extended names can be created with the option disabled. This state is only +meant to facilitate downgrading or reverting the option change. When the option +is set to `false`, all database objects with extended names that were created +in the meantime should be removed manually. + ## Miscellaneous changes ### In-memory edge cache startup options and metrics From d5a2fb3dbe62600fed01b245621b97735cf56360 Mon Sep 17 00:00:00 2001 From: Paula Mihu <97217318+nerpaula@users.noreply.github.com> Date: Thu, 19 Oct 2023 15:20:39 +0200 Subject: [PATCH 2/2] mention behavior change in the api changes page as well --- .../release-notes/version-3.12/api-changes-in-3-12.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/site/content/3.12/release-notes/version-3.12/api-changes-in-3-12.md b/site/content/3.12/release-notes/version-3.12/api-changes-in-3-12.md index 89839ed758..71b5b0071a 100644 --- a/site/content/3.12/release-notes/version-3.12/api-changes-in-3-12.md +++ b/site/content/3.12/release-notes/version-3.12/api-changes-in-3-12.md @@ -14,6 +14,8 @@ integrations for ArangoDB 3.12. ### Behavior changes +#### HTTP headers + The following long-deprecated features have been removed from ArangoDB's HTTP server: @@ -34,6 +36,12 @@ server: The functionality has now been removed and setting the startup option does nothing. +#### `--database.extended-names` enabled by default + +The `--database.extended-names` startup option is now enabled by default. +The names of databases, collections, Views, and indexes may contain Unicode +characters using the default settings. + #### Collection API When creating a collection using the `POST /_api/collection` endpoint, the