|
| Re: Problem with Jubula8 and MySQL [message #1352379 is a reply to message #1352211] |
Tue, 13 May 2014 12:39   |
|
This is caused by a limitation of MySQL which limits the size of a table row (precisely the sum of varchar2 columns) to 64k. We are looking into this and will try to reduce the size. We are not sure right now if we will release a new version since MySQL is not supported. We might just provide a few replacement jars to help those who use MySQL.
- Achim
|
|
|
| Re: Problem with Jubula8 and MySQL [message #1352414 is a reply to message #1352379] |
Tue, 13 May 2014 12:55 |
 Dominik Gabriel
Messages: 113
Registered: June 2013 |
Senior Member |
|
|
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 12:56] Report message to a moderator |
|
|
| Re: Problem with Jubula8 and MySQL [message #1356902 is a reply to message #1352414] |
Thu, 15 May 2014 09:18 |
|
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.01443 seconds
] 
Search
Help
Register
Login
Home
