Bug #41242 Automation of DbDoc reporting
Submitted: 4 Dec 2008 19:24 Modified: 15 Dec 2008 13:11
Reporter: Richard Piatkowski Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Workbench Severity:S4 (Feature request)
Version:5.0.27 SE OS:Microsoft Windows (SP2)
Assigned to: CPU Architecture:Any
Tags: Automation, DBDoc
Triage: Triaged: D5 (Feature request) / R3 (Medium) / E3 (Medium)

[4 Dec 2008 19:24] Richard Piatkowski
Description:
While documenting the database layout of a bigger project I really missed a possibility to automate the creation of DbDoc-Documents. It would be nice to create a DbDoc configuration and to relaunch the creation process with an single click.

How to repeat:
Missing feature.
[15 Dec 2008 11:22] Susanne Ebrecht
Many thanks for writing a feature request.
Please, would you give some more details, what you miss?

What exactly you want to document and how should such a feature work? Where is the use case?
[15 Dec 2008 11:32] Richard Piatkowski
When working in a team environment, we are using continuous integration methods whereever possible.

When I am creating a database model report through DbDoc I can custumize my report by changing:

- template
- style
- title
- output directory
- content options
- ...

Every time I generate a report, I have to reconfigure the reporting options. It is not possible to create a configuration file for DbDoc, so I have to reconfigure everything manually. It takes only one minute, but repeating this steps several times a day is boring and unnecessary.

Additionally to this, it would be very helpful to create the report from the command-line, like in this pseudo-query:

createdbdoc.exe -c dbdoc_config_file.cfg myworkbenchmodel.mwb

The config_file.cfg contains all configuration and the report could be generated by an automated system. So it would be possible to create an update of the DbDoc-documentation automatically every time a developer checks in a new version in our subversion repository system.
[15 Dec 2008 13:11] Susanne Ebrecht
Many thanks for your quick answer. We will discuss this internally.