Instead, it is accessed through session.get(to_be_queried, key).

Changes most of the `relation` calls to `relationship` calls per the
warning messages. However, this causes at least one error due to a
nuance in how `relation` works, it seems, and that needs to be
diagnosed.

This non-sql related update catches the base exception caught in
FileOpser.fileop and adds its message to the FileOpser.doerror message.

This is mainly for convenience with updating, and can be omitted later
if desired.

This overrides SQLAlchemy's declarative_base in both instances when
creating the declarative base class.

… on session not engine

…ce of ordering

… the work for the summit and archive releases