Shift Fannie to using models to create tables instead of the
CREATE scripts. Upsides are eliminating duplicate code as
well as increased testability. Pulling available models
and creating the structures in test databases will be
much more scriptable.
Merge branch 'fannieDevelop' into fannieInstallFromModels
Restructured Fannie operation DB creation (core_op) to use models.
Made some adjustments to make the function unit testable. The
InstallTest will create a database named "unit_test_op" and verify
all the tables/views get built correctly.
Merge branch 'fannieDevelop' into fannieInstallFromModels
Replaced part of Fannie trans db creation with models
Unit-testing trans db creation
More trans tables created from models. Added secondary dtransaction-schema
models for table/view creation but still using DTransactionsModel
for unified updates & column changes
Remove usage of old ProductsModel static methods
Merge branch 'fannieDevelop' into fannieInstallFromModels

Conflicts:
	fannie/batches/UNFI/load-classes/UnfiUploadPage.php
More core_trans views created via models
Model-solution for creating views that reference both core_op
and core_trans.
Merge branch 'fannieInstallFromModels' into fannieDevelop
BUGFIX: manipulate underlying ADOdb $database setting when changing
connection's default db
Wrapped up building core_trans from models as well as building
unit_test_trans for unit tests
Avoid stray apostrophes dealing with member card UPCs
Turn OBF more towards rolling sale projections
Start unit testing trans_archive structures in unit_test_archive
Deprecate summary tables in trans_archive. They're duplicated by
the CoreWarehouse plugin.
Full Fannie table/view creation via models with unit testing
Example unit test for TransArchiveTask monthly table creation