| Problem with Jubula8 and MySQL [message #1352211] |
Tue, 13 May 2014 06:57  |
Eclipse User |
|
|
|
Hi,
I have a problem with MySQL. I generated a new DB-schema and connected to it with jubula. the unbound modules were automatically be importet but if i run a test i haven't any result details. when i looked in the .log i saw there is an exeption that says that the table TESTRESULT is missing. when i look in database there really is no table calles TESTRESULT.
can anybody help me?
|
|
|
|
| Re: Problem with Jubula8 and MySQL [message #1352414 is a reply to message #1352379] |
Tue, 13 May 2014 08:55  |
| Eclipse User |
|
|
|
i created the table manually by a SQL statement:
CREATE TABLE `jubula8_0`.`TESTRESULT` (
`ID` bigint(19) NOT NULL,
`ACTION_NAME` varchar(3800) DEFAULT NULL,
`STATUS_ACTUAL_VALUE` varchar(3800) DEFAULT NULL,
`COMPONENT_NAME` varchar(3800) DEFAULT NULL,
`COMPONENT_TYPE` varchar(3800) DEFAULT NULL,
`STATUS_EXPECTED_VALUE` varchar(3800) DEFAULT NULL,
`SCREENSHOT` longblob,
`INTERNAL_ACTION_NAME` varchar(3800) DEFAULT NULL,
`INTERNAL_COMPONENT_NAME` varchar(3800) DEFAULT NULL,
`INTERNAL_COMPONENT_TYPE` varchar(3800) DEFAULT NULL,
`INTERNAL_KEYWORD_GUID` varchar(3800) DEFAULT NULL,
`INTERNAL_KEYWORD_STATUS` int(10) NOT NULL,
`INTERNAL_KEYWORD_TYPE` int(10) NOT NULL,
`INTERNAL_PARENT_KEYWORD_ID` bigint(19) DEFAULT NULL,
`INTERNAL_TESTRUN_ID` bigint(19) DEFAULT NULL,
`KEYWORD_COMMENT` varchar(3800) DEFAULT NULL,
`KEYWORD_LEVEL` int(10) NOT NULL,
`KEYWORD_NAME` varchar(3800) DEFAULT NULL,
`KEYWORD_SEQUENCE` int(10) NOT NULL,
`KEYWORD_STATUS` varchar(3800) DEFAULT NULL,
`KEYWORD_TYPE` varchar(3800) DEFAULT NULL,
`OM_NO_SIMILAR_COMPONENTS` int(10) NOT NULL,
`OM_HEURISTIC_EQUIVALENCE` double NOT NULL,
`STATUS_DESCRIPTION` varchar(3800) DEFAULT NULL,
`STATUS_OPERATOR` varchar(3800) DEFAULT NULL,
`STATUS_TYPE` varchar(3800) DEFAULT NULL,
`TASK_ID` varchar(3800) DEFAULT NULL,
`TIMESTAMP` datetime DEFAULT NULL,
`INTERNAL_VERSION` int(10) DEFAULT NULL,
PRIMARY KEY (`ID`),
KEY `PI_TESTRUN_ID` (`INTERNAL_TESTRUN_ID`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1;
i created the varchars with 3,8k instead of 4k. could this cause any problems? i tried it out and it seems to work
to find out what collumns are needed i generated a H2 database and inspected it
[Updated on: Tue, 13 May 2014 08:56] by Moderator |
|
|
| Re: Problem with Jubula8 and MySQL [message #1356902 is a reply to message #1352414] |
Thu, 15 May 2014 05:18 |
| Eclipse User |
|
|
|
Frankly, I don't know if this may cause problems. We are using EclipseLink as an OR Mapper and some internals might not like differences between the JPA description and the actual DB scheme. You should at least export/import your project when switching to the next (future) version of Jubula since there might be problems with future versions of EclipseLink.
- Achim
|
|
|
Powered by
FUDForum. Page generated in 0.25297 seconds
Home