Proposals for DB Schema Changes: Difference between revisions
Jump to navigation
Jump to search
Line 15: | Line 15: | ||
===Partner Module=== | ===Partner Module=== | ||
''(none yet)'' | |||
===Personnel Module=== | ===Personnel Module=== | ||
''(none yet)'' | |||
===Conference Module=== | ===Conference Module=== | ||
''(none yet)'' | |||
===Financial Development Module=== | ===Financial Development Module=== | ||
''(none yet)'' | |||
===System Manager Module=== | ===System Manager Module=== | ||
''(none yet)'' | |||
===DB Tables That Are 'Common', That Is, Used by More Than One Module=== | ===DB Tables That Are 'Common', That Is, Used by More Than One Module=== | ||
''(none yet)'' | |||
==Former Proposals That Have Been Implemented by Now== | ==Former Proposals That Have Been Implemented by Now== | ||
''(none yet)'' | ''(none yet)'' |
Latest revision as of 16:50, 17 September 2015
Landing Page for Proposals for DB Schema Changes
This page serves as a collection for proposals for re-designing existing OpenPetra DB Tables or of proposals for the introduction of new OpenPetra DB Tables, that is, of DB schema changes.
Important
- Each proposal should be put on its own wiki page so that the present page only presents the collection of proposals and not the actual proposals;
- Each wiki page title for such a proposal should be short and descriptive and contain the name of the developer that wrote that proposal in brackets at the end of the description. Example: Splitting of a_ledger DB Table (ChristopherT)
- A Bug should be created in our tracker that references the wiki page for such a proposal. That gives visibility to project management and allows appropriate planning and prioritisation.
Once a proposal has been implemented it should be moved out of the 'Proposals' section and into the 'Former Proposals That Have Been Implemented by Now' section!
Proposals
Finance Module
Partner Module
(none yet)
Personnel Module
(none yet)
Conference Module
(none yet)
Financial Development Module
(none yet)
System Manager Module
(none yet)
DB Tables That Are 'Common', That Is, Used by More Than One Module
(none yet)
Former Proposals That Have Been Implemented by Now
(none yet)