| | 1 | This page hosts the detailed specification for the [https://blueprints.launchpad.net/sahana3/+spec/bzr-hooks Blueprint for Bzr Hooks for Committers]. |
| | 2 | |
| | 3 | It is for working on tools to enhance the process for committers to Trunk: DeveloperGuidelinesBzr |
| | 4 | |
| | 5 | == Problem Statement == |
| | 6 | We use the database to store key reference data which should be available to any new instance. |
| | 7 | We also use the database to create test data which shouldn't be present for new instances. |
| | 8 | |
| | 9 | We need a tool to populate the database with reference data.[[BR]] |
| | 10 | This is like {{{gis_conf.inc}}} & {{{mysql-config.sql}}} for S2 |
| | 11 | |
| | 12 | We need a tool to empty the databases (& reset IDs).[[BR]] |
| | 13 | The development database is sqlite: |
| | 14 | {{{ |
| | 15 | sqlite3 storage.db ???? |
| | 16 | }}} |
| | 17 | http://sqlite.org/lang_vacuum.html ? |
| | 18 | |
| | 19 | These tools should be triggered via a Bzr start-commit-hook. |
| | 20 | |
| | 21 | === Reference Data === |
| | 22 | module, x_menu_option, gis_config, gis_projection, gis_marker |
