Community
Participate
Working Groups
Jubula doesn't work if the character set of the database used is utf8. This is tested on MySQL but I guess the same thing should show up on any other SQL database. The problem seems to be that Jubula can't import the base projects unbound_modules_* and then it's impossible to create or import a new project. No meaningful error message is given, so that it took me some hours to track down the problem.
Created attachment 206589 [details] Error thrown when trying to import my project Same problem here. When I tried to select my MySQL database (db encoding = utf8), the initial import of the module projects failed: --- Connection to Database successful. Importing projects... Reading projects... Reading project file /resources/library/unbound_modules_html_5.2.xml. Reading project file /resources/library/unbound_modules_rcp_5.2.xml. Reading project file /resources/library/unbound_modules_concrete_5.2.xml. Reading project file /resources/library/unbound_modules_swt_5.2.xml. Project "unbound_modules_swt" in version 5.2 requires the following project(s): - project "unbound_modules_concrete" in version 5.2 --- When I tried to import my existing project afterwards, the attached error was thrown. Everything works now fine after changing the encoding of the database to latin1. As I do not depend on the utf8 encoding this is no problem for me but it should at least be documented in the installation because it took me quite some time to figure this out. Reproducable: always Jubula Version: 1.1.0 Steps to reproduce: 1. Setup a MySQL-Database with option "character_set_database" set to "utf8" 2. Setup db connection in Jubula 3. Connect to db in Jubula --> Importing project fails! 4. Try to import an existing Jubula project --> Attached exception is trhown
UTF-8 is working on Oracle and H2 which are the only databases we test. H2 should not be used for production uses. MySQL and Postgres are only there for convenience. There are configurations which will work with Jubula, but we are no experts on the DBs.
*** Bug 400656 has been marked as a duplicate of this bug. ***
