`wutta_corepos.conf`¶

App Configuration

class wutta_corepos.conf.WuttaCoreposConfigExtension[source]¶

App config extension for Wutta-COREPOS.

This does some CORE DB connection setup based on config. It will create three sets of DB engines, and establish one primary engine for each set. The sets correspond to CORE Office DB types:

office_op (default name core_op)
office_trans (default name core_trans)
office_arch (default name trans_archive)

The config object will be given the following attributes:

core_office_op_engine¶: Primary engine for the office_op DB. May be null if no config is found.

core_office_op_engines¶: Dict of office_op DB engines. May be empty if no config is found; otherwise there should at least be a default key defined, corresonding to core_office_op_engine.

core_office_trans_engine¶: Primary engine for the office_trans DB. May be null if no config is found.

core_office_trans_engines¶: Dict of office_trans DB engines. May be empty if no config is found; otherwise there should at least be a default key defined, corresonding to core_office_trans_engine.

core_office_arch_engine¶: Primary engine for the office_arch DB. May be null if no config is found.

core_office_arch_engines¶: Dict of office_arch DB engines. May be empty if no config is found; otherwise there should at least be a default key defined, corresonding to core_office_arch_engine.

core_lane_op_engine¶: Primary engine for the lane_op DB. May be null if no “default” engine is configured - which is typical for a multi-lane environment. See core_lane_op_engines for the full set.

core_lane_op_engines¶: Dict of lane_op DB engines. May be empty if no config is found; otherwise keys are typically like 01 and 02 etc. If present, the default key will correspond to core_lane_op_engine.

core_lane_trans_engine¶: Primary engine for the lane_trans DB. May be null if no “default” engine is configured - which is typical for a multi-lane environment. See core_lane_trans_engines for the full set.

core_lane_trans_engines¶: Dict of lane_trans DB engines. May be empty if no config is found; otherwise keys are typically like 01 and 02 etc. If present, the default key will correspond to core_lane_trans_engine.