From 9c05baafba1f9c5717915be5ea4a6b29f0704ee6 Mon Sep 17 00:00:00 2001 From: Boris Kolpackov Date: Wed, 4 Aug 2021 08:35:05 +0200 Subject: Throw unknown_schema_version from migrate() if database is too new --- doc/manual.xhtml | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/doc/manual.xhtml b/doc/manual.xhtml index f7fe095..0b6dc08 100644 --- a/doc/manual.xhtml +++ b/doc/manual.xhtml @@ -4578,9 +4578,9 @@ namespace odb

The unknown_schema exception is thrown by the odb::schema_catalog class if a schema with the specified name is not found. Refer to Section 3.4, "Database" - for details. The unknown_schema_version exception is - thrown by the schema_catalog functions that deal with - database schema evolution if the passed version is unknow. Refer + for details. The unknown_schema_version exception is thrown + by the schema_catalog functions that deal with database + schema evolution if the passed or current version is unknow. Refer to Chapter 13, "Database Schema Evolution" for details.

@@ -12841,7 +12841,7 @@ namespace odb
  1. The database administrator determines the current database version. If migration is required, then for each migration step (that - is, from one version to the next), he performs the following:
  2. + is, from one version to the next), they perform the following:
  3. Execute the pre-migration file.
  4. @@ -13003,12 +13003,12 @@ t.commit (); process is directed by an external entity, such as a database administrator or a script.

    -

    Most schema_catalog functions presented above also - accept the optional schema name argument. If the passed schema - name is not found, then the odb::unknown_schema exception - is thrown. Similarly, functions that accept the schema version - argument will throw the odb::unknown_schema_version exception - if the passed version is invalid. Refer to Section +

    Most schema_catalog functions presented above also accept + the optional schema name argument. If the passed schema name is not + found, then the odb::unknown_schema exception is + thrown. Similarly, functions that accept the schema version argument will + throw the odb::unknown_schema_version exception if the + passed or current version is invalid. Refer to Section 3.14, "ODB Exceptions" for more information on these exceptions.

    To illustrate how all these parts fit together, consider the -- cgit v1.1