|How to let Jubula "forget" a database [message #734997]
||Mon, 10 October 2011 11:39
| Niels K
Registered: July 2011
I am trying out the new Jubula release, I'm curious about the new features.
I am using Jubula with a mySql DB. When connecting to the DB with Jubula 1.1 for the first time, a migration assistant appears, does some changes in the DB and after this, I cant open any test... hmm ok, I didn't expect everything to work correctly.
So I tried a workaround: Exported my test to xml (before staring the migration), created a new DB(for unproductive usage), connected to this (emtpy) DB with Jubula 1.1. Jubula created the tables as usual when connecting to an emtpy DB for the first time. Then I imported the test from the xml file and everything works ok. Fine.
Now I want to perform theese steps on my productive DB which I used with Jubula 1.0 before. I deleted every table from this DB manually and expected Jubula 1.1 would create its tables as usual when connecting to an emtpy DB... but it doesn't.
It seems that Jubula remebers this DB and expects to find its structure there, does nit find it and returns an error. (In fact, Jubula 1.1 did know my database connecting just after the installation).
To cut the long story short, how can I let Jubula "forget" a database, so that when I connect to this (cleared) database, Jubula creates its initial structure again?
(System is WinXP)
Thanks for the answer,
|Re: How to let Jubula "forget" a database [message #735154 is a reply to message #734997]
||Tue, 11 October 2011 02:23
| Alexandra Schladebeck
Registered: July 2009
Niels K wrote on Mon, 10 October 2011 17:39|
a migration assistant appears, does some changes in the DB and after this, I cant open any test... hmm ok, I didn't expect everything to work correctly.
The migration assistant clears the database, including all the projects in it. The text of the wizard explains quite explicitly that you have to first export any projects you want to keep and then import them at the end. Exporting first, then connecting to the database and performing migration is the documented workflow:
The database information is stored in the preferences, so it is workspace-specific. You might want to look at these links for more information:
[Updated on: Tue, 11 October 2011 02:24]
Report message to a moderator
Powered by FUDForum
. Page generated in 0.05709 seconds