Description:
I'm just beginning to get using Workbench in ernest, and am using it for my second project. Something I realised is that the database design for several projects will have common elements. For example, if I am creating a website application that performs e-commerce using 'PayPal Instant Payment Notification', then I will always want a table or two in order to store that PayPal IPN data. These tables are going to be dictated by the IPN specification and will be identical regardless of the application.
In that case it would be nice to be able to import/export fragments of a database model. In essence this gives the ability to create a library of pre-made tables and relations that can be imported into other models.
The PayPal IPN use-case is the first I could think of, but it could also be relevant for a `member` table storing username, email address, password hash etc? I'm sure there are many other use cases where (in any given application) some of the tables and db design is 'boilerplate' and could be fulfilled (or nearly-fulfilled) by inserting relevant objects from a library.
How to repeat:
N/A - feature request
Suggested fix:
Suggestion (in the first instance) is some kind of "export model fragment" functionality, along with "import objects from fragment".
A full library/browser could be added later, but maybe only if the import/export feature is popular.
If it really becomes popular then possibly a collection of pre-made fragments could be created for various purposes and shipped with workbench (or made available through a web-based repository).
