Draft comments (auto saved) are included in comment notifications

Brendan Humphreys Replied
re: revision External DB Spec (lines 79)(see https://extranet.atlassian.com/crucible/cru/CR-FE-861#c7160 ) :-

h3. Setup new instance to point to custom db

* User runs Crucible for the first time, they are presented with the existing setup screen
* They are asked if they want to use an external db
* They are presented with the setup jdbc wizard (as above)
**  They can choose a dialect. This selects a default driver class.
*** One dialect is "built-in" in which all the other fields are hidden.
** They enter in jdbc url, username/password and optional properties.
** They can hit "test connection" which reports on the ability to connect to the db.
** They hit "Next > create scheme" which creates the schema
** Any errors and they are shown and they bounced to the enter-jdbc screen to try again

In reponse to thread:
(Brendan Humphreys) none of these usecases invoke GUI admin screens. I think they all should.

h3. Migrate to a new database type.

* Go to admin, go to Migrate to Other DB section
* User is prompted with "setup jdbc" wizard/screen (see below)
* User enters jdbc details, can test the connection.
* User clicks Next-Perform Migration which
** puts app into export mode
** exports jdbc and plugins (see inport/export doc)
** swaps the connection manager to the new jdbc location.
** runs an import of what was just exported
** Displays progress of the above on-screen
* saves changes to config.xml (ie jdbc change is not persisted until re-import works)

> > (Peter McNeil) I think that is a stretch goal for database, perhaps after we have import/export which will no doubt be after external DBs are enabled (with no data migration).

I'm not saying that it's not doable by 2.0 but for this spec and the inital release.... So are we specing out