Move indexes from model scope to table scope

Conceptually, indexes belong to tables and some databases (MySQL, MSSQL)
indeed treat them as such (i.e., you can have indexes with the same name
in different tables).

1 files changed, 4 insertions, 4 deletions

diff --git a/odb/semantics/relational/elements.hxx b/odb/semantics/relational/elements.hxx
index 6b4964e..8eb695a 100644
--- a/odb/semantics/relational/elements.hxx
+++ b/odb/semantics/relational/elements.hxx
@@ -174,10 +174,10 @@ namespace semantics
     public:
       // Id identifies the C++ node (e.g., a class or a data member) that
       // this model node corresponds to. The ids are not necessarily unique
-      // (e.g., there can be a table and an index with the same id that
-      // correspond to a container member). However, in any given scope,
-      // the {id,typeid} must be unique. This becomes important when we
-      // try to find correspondance between nodes during model diff'ing.
+      // (e.g., there can be a foreign key and an index with the same id that
+      // correspond to a container member). However, in any given scope, the
+      // {id,typeid} must be unique. This becomes important when we try to
+      // find correspondance between nodes during model diff'ing.
       //
       nameable (string const& id): id_ (id), named_ (0) {}