From 9c05baafba1f9c5717915be5ea4a6b29f0704ee6 Mon Sep 17 00:00:00 2001
From: Boris Kolpackov 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.
Most Most To illustrate how all these parts fit together, consider the
--
cgit v1.1
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
+ 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.