Rename from default/new to singlehost/multihost to match 25.10

Author: badlop

content/admin/configuration/database.md

@@ -74,7 +74,7 @@ with the [`default_db`](toplevel.md#default_db) top-level option:
 
 def:update
 : Modify the database schema and all its tables to match the installed ejabberd version.
-  Not to be confused with [upgrade ejabberd](def:upgrade) or [switch schema](def:switch).
+  Not to be confused with [upgrade ejabberd](def:upgrade) or [convert schema](def:convert).
 
 The [update_sql_schema](toplevel.md#update_sql_schema) top-level option
 allows ejabberd to create and update the tables automatically in the SQL database
@@ -103,36 +103,38 @@ The SQL database schema files are available:
 See [ejabberd SQL Database Schema](../../developer/sql-schema.md)
 for details on database schemas.
 
-## _Default_ and _New_ Schemas
+## _Singlehost_ or _Multihost_
+
+<!-- md:version renamed from default/new to singlehost/multihost in [25.10](../../archive/25.10/index.md) -->
 
 If using MySQL, PostgreSQL, Microsoft SQL or SQLite,
 you can choose between two database schemas:
 
-- the _default_ schema is preferable when serving one massive domain,
-- the _new_ schema is preferable when serving many small domains.
+- the _singlehost_ schema is preferable when serving one massive domain, or just a few domains,
+- the _multihost_ schema is preferable when serving many small domains.
 
-The _default_ schema stores only one XMPP domain in the database.
+The _singlehost_ schema stores only one XMPP domain in the database.
 The [XMPP domain](basic.md#xmpp-domains)
 is not stored as this is the same for all the accounts,
 and this saves space in massive deployments.
 However, to handle several domains,
 you have to setup one database per domain
 and configure each one independently
 using [host_config](basic.md#virtual-hosting),
-so in that case you may prefer the _new_ schema.
+so in that case you may prefer the _multihost_ schema.
 
-The _new_ schema stores the XMPP domain in a new column `server_host`
+The _multihost_ schema stores the XMPP domain in a new column `server_host`
 in the database entries,
 so it allows to handle several XMPP domains in a single ejabberd database.
 Using this schema is preferable when serving several XMPP domains
 and changing domains from time to time.
-However, if you have only one massive domain, you may prefer to use the _default_ schema.
+However, if you have only one massive domain, you may prefer to use the _singlehost_ schema.
 
-To use the _new_ schema, edit the ejabberd configuration file and enable
-[new_sql_schema](toplevel.md#new_sql_schema) top-level option:
+To use the _multihost_ schema, edit the ejabberd configuration file and enable
+[sql_schema_multihost](toplevel.md#sql_schema_multihost) top-level option:
 
 ``` yaml
-new_sql_schema: true
+sql_schema_multihost: true
 ```
 
 When creating the tables, if ejabberd can use the [update_sql_schema](toplevel.md#update_sql_schema)
@@ -141,29 +143,29 @@ it will take care to create the tables with the correct schema.
 
 On the other hand, if you are creating the tables manually,
 remember to use the proper SQL schema!
-For example, if you are using MySQL and choose the _default_ schema, use `mysql.sql`.
-If you are using PostgreSQL and need the _new_ schema, use `pg.new.sql`.
+For example, if you are using MySQL and choose the _singlehost_ schema, use `mysql.sql`.
+If you are using PostgreSQL and need the _multihost_ schema, use `pg.new.sql`.
 
-def:switch
-: Change the database schema and all its tables from `default` schema to `new` schema.
+def:convert
+: Change the database schema and all its tables from `singlehost` schema to `multihost` schema.
   Not to be confused with [upgrade ejabberd](def:upgrade) or [update schema](def:update).
 
-If you already have a MySQL or PostgreSQL database with the _default_ schema and contents,
-you can switch it to the _new_ schema:
+If you already have a MySQL or PostgreSQL database with the _singlehost_ schema and contents,
+you can convert it to the _multihost_ schema:
 
 * *MySQL*:
 Edit the file `sql/mysql.old-to.new.sql` which is included with ejabberd,
 fill DEFAULT_HOST in the first line,
 and import that SQL file in your database.
-Then enable the `new_sql_schema` option in the ejabberd configuration,
+Then enable the `sql_schema_multihost` top-level option in the ejabberd configuration,
 and restart ejabberd.
 
 * *PostgreSQL*:
-First enable `new_sql_schema` and
+First enable the `sql_schema_multihost` top-level option and
 [mod_admin_update_sql](modules.md#mod_admin_update_sql)
 in your ejabberd configuration:
     ``` yaml
-    new_sql_schema: true
+    sql_schema_multihost: true
     modules:
       mod_admin_update_sql: {}
     ```
@@ -197,7 +199,7 @@ To configure SQL there are several top-level options:
 - [sql_start_interval](toplevel.md#sql_start_interval)
 - [sql_prepared_statements](toplevel.md#sql_prepared_statements)
 - [update_sql_schema](toplevel.md#update_sql_schema), see section [Database Schema](#database-schema)
-- [new_sql_schema](toplevel.md#new_sql_schema), see section [Default and New Schemas](#default-and-new-schemas)
+- [sql_schema_multihost](toplevel.md#sql_schema_multihost), see section [Singlehost or Multihost](#singlehost-or-multihost)
 
 Example of plain ODBC connection:
 

content/admin/configuration/modules.md

@@ -152,9 +152,9 @@ ejabberdctl srg_create g1 example.org "'Group number 1'" this_is_g1 g1
 mod\_admin\_update\_sql
 -----------------------
 
-This module can be used to update existing SQL database from the default
-to the new schema. Check the section
-[Default and New Schemas](database.md#default-and-new-schemas) for
+This module can be used to convert your existing SQL database from the
+singlehost to the multihost schema. Check the section
+[Singlehost or Multihost](database.md#singlehost-or-multihost) for
 details. Please note that only MS SQL, MySQL, and PostgreSQL are
 supported. When the module is loaded use [update_sql](../../developer/ejabberd-api/admin-api.md#update_sql) API.
 

content/admin/configuration/toplevel.md

@@ -1795,7 +1795,7 @@ value defined in [queue_type](#queue_type) or `ram` if the latter is not set.
 <!-- md:version renamed in [25.10](../../archive/25.10/index.md) -->
 
 Whether to use the
-[multihost SQL schema](database.md#default-and-new-schemas). All
+[multihost SQL schema](database.md#singlehost-or-multihost). All
 schemas are located at
 <https://github.com/processone/ejabberd/tree/25.10/sql>. There are two
 schemas available. The legacy `singlehost` schema stores one XMPP domain
@@ -1804,8 +1804,8 @@ XMPP domains in a single ejabberd database. The `multihost` schema is
 preferable when serving several XMPP domains and/or changing domains
 from time to time. This avoid need to manage several databases and
 handle complex configuration changes. The default depends on
-configuration flag `--enable-sql-schema-multihost` which is set at
-compile time.
+[./configure](../install/source.md#configure) flag
+`--enable-sql-schema-multihost` which is set at compile time.
 
 ## sql\_server
 

content/admin/install/source.md

@@ -138,25 +138,25 @@ This account needs a HOME directory, because the [Erlang cookie file](../guide/s
     <!-- md:version added in [21.04](../../archive/21.04/index.md) -->
 
 - **`--enable-mssql`**: Enable Microsoft SQL Server support, this
-    option requires --enable-odbc (see [Supported storages][18]).
+    option requires --enable-odbc (see [Supported storages](../configuration/database.md#supported-storages)).
 
-- **`--enable-mysql`**: Enable MySQL support (see [Supported storages][18]).
-
-- **`--enable-new-sql-schema`**: Use new SQL schema.
+- **`--enable-mysql`**: Enable MySQL support (see [Supported storages](../configuration/database.md#supported-storages)).
 
 - **`--enable-odbc`**: Enable pure ODBC support.
 
 - **`--enable-pam`**: Enable the PAM authentication method (see [PAM Authentication](../configuration/authentication.md#pam-authentication) section).
 
-- **`--enable-pgsql`**: Enable PostgreSQL support (see [Supported storages][18]).
+- **`--enable-pgsql`**: Enable PostgreSQL support (see [Supported storages](../configuration/database.md#supported-storages)).
 
 - **`--enable-redis`**: Enable Redis support to use for external session storage.
 
 - **`--enable-roster-gateway-workaround`**: Turn on workaround for processing gateway subscriptions.
 
 - **`--enable-sip`**: Enable SIP support.
 
-- **`--enable-sqlite`**: Enable SQLite support (see [Supported storages][18]).
+- **`--enable-sql-schema-multihost`**: Use multihost SQL schema by default.
+
+- **`--enable-sqlite`**: Enable SQLite support (see [Supported storages](../configuration/database.md#supported-storages)).
 
 - **`--disable-stun`**: Disable STUN/TURN support.
 

content/admin/upgrade/index.md

@@ -2,12 +2,12 @@
 
 def:upgrade
 : Install a version of the program newer than the currently installed one.
-  Not to be confused with [update](def:update) or [switch schema](def:switch).
+  Not to be confused with [update](def:update) or [convert schema](def:convert).
 
 def:update
 : Modify your program installation to match the requirements of the new program version.
   This usually involves updating your configuration, your database schema, your API client, your custom modules...
-  Not to be confused with [upgrade ejabberd](def:upgrade) or [switch schema](def:switch).
+  Not to be confused with [upgrade ejabberd](def:upgrade) or [convert schema](def:convert).
 
 This document contains administration procedure for each version upgrade.
 Only upgrade from version N to N+1 is documented and supported.

content/archive/20.12/modules.md

@@ -82,7 +82,7 @@ mod\_admin\_update\_sql
 
 This module can be used to update existing SQL database from the default
 to the new schema. Check the section [Default and New
-Schemas](../../admin/configuration/database.md#default-and-new-schemas) for details.
+Schemas](../../admin/configuration/database.md#singlehost-or-multihost) for details.
 When the module is loaded use *update\_sql* ejabberdctl command.
 
 The module has no options.

content/archive/21.01/modules.md

@@ -82,7 +82,7 @@ mod\_admin\_update\_sql
 
 This module can be used to update existing SQL database from the default
 to the new schema. Check the section [Default and New
-Schemas](../../admin/configuration/database.md#default-and-new-schemas) for details.
+Schemas](../../admin/configuration/database.md#singlehost-or-multihost) for details.
 When the module is loaded use *update\_sql* ejabberdctl command.
 
 The module has no options.

content/archive/21.04/modules.md

@@ -82,7 +82,7 @@ mod\_admin\_update\_sql
 
 This module can be used to update existing SQL database from the default
 to the new schema. Check the section [Default and New
-Schemas](../../admin/configuration/database.md#default-and-new-schemas) for details.
+Schemas](../../admin/configuration/database.md#singlehost-or-multihost) for details.
 When the module is loaded use *update\_sql* ejabberdctl command.
 
 The module has no options.

content/archive/21.07/modules.md

@@ -82,7 +82,7 @@ mod\_admin\_update\_sql
 
 This module can be used to update existing SQL database from the default
 to the new schema. Check the section [Default and New
-Schemas](../../admin/configuration/database.md#default-and-new-schemas) for details.
+Schemas](../../admin/configuration/database.md#singlehost-or-multihost) for details.
 Please note that only PostgreSQL is supported. When the module is loaded
 use *update\_sql* ejabberdctl command.
 

content/archive/21.12/modules.md

@@ -82,7 +82,7 @@ mod\_admin\_update\_sql
 
 This module can be used to update existing SQL database from the default
 to the new schema. Check the section [Default and New
-Schemas](../../admin/configuration/database.md#default-and-new-schemas) for details.
+Schemas](../../admin/configuration/database.md#singlehost-or-multihost) for details.
 Please note that only PostgreSQL is supported. When the module is loaded
 use [update_sql](admin-api.md#update_sql) API.