Inheritance diagram for CoreWarehouse:
Public Member Functions | |
| setting_change () | |
 Public Member Functions inherited from COREPOS\Fannie\API\FanniePlugin | |
| pluginEnable () | |
| plugin_enable () | |
| pluginDisable () | |
| plugin_disable () | |
| settingChange () | |
| setting_change () | |
| pluginUrl () | |
| plugin_url () | |
| pluginDir () | |
| plugin_dir () | |
| pluginDbStruct ($db, $struct_name, $db_name="") | |
| plugin_db_struct ($db, $struct_name, $db_name="") | |
Public Attributes | |
| $plugin_settings | |
| $plugin_description | |
| Public Attributes inherited from COREPOS\Fannie\API\FanniePlugin | |
| $plugin_settings | |
| $plugin_description = 'This author didn\'t provide anything. Shame!' | |
Additional Inherited Members | |
| Static Public Member Functions inherited from COREPOS\Fannie\API\FanniePlugin | |
| static | memberOf ($file) |
| static | isEnabled ($plugin) |
| static | pluginMap ($path="", $in=array()) |
Member Data Documentation
| CoreWarehouse::$plugin_description |
Initial value:
= 'Plugin for managing data warehouse. No end-user facing
functionality here. The plugin is just a set of tools for creating summary
tables and loading historical transaction data into said tables. Reports may
utilize the warehouse when available. In some cases it may just mean simpler
queries; in others there may be a performance benefit to querying
pre-aggregated data.'
| CoreWarehouse::$plugin_settings |
Initial value:
= array(
'WarehouseDatabase' => array('default'=>'core_warehouse','label'=>'Database',
'description'=>'Database to store transaction information. Can
be one of the default CORE databases or a
separate one.')
)
Desired settings. These are automatically exposed on the 'Plugins' area of the install page and written to ini.php
The documentation for this class was generated from the following file:
- fannie/modules/plugins2.0/CoreWarehouse/CoreWarehouse.php
