Hello,
I just run freshly installed ProjeQtOr version 10.0.1 on latest WAMP64 and my first admin logon generates a lot of errors during database creation.
From MySQL log I can see number of tables are not created from the same reason, record is to big to fit to database definition what is strange because neither CREATE TABLE statement defines record so big.
I am using MySQL server 8.0.16.
I attached complete log.
Any idea what went wrong?
Hello,
What is your charset ?
You should use utf8mb4_general_ci charset.
cordially
Hi.
Don't think that is the reason.
I dropped invalid projeqtor database, installed ProjeQtOr v9.5.5, logged as admin and its database was successfully created, no errors reported. Following update to latest version 10.0.1 executed with no errors and I was able to start and use ProjeQtOr.
Attached are logs from both, version 9.5.5 installation and update to version 10.0.1.
Regards
Hello,
I have the exact same problem when I start with a clean install (no data).
The error message (multiple occurrences):
2022-07-15 16:57:54.771 ** ERROR ** Exception-[42000] SQLSTATE[42000]: Syntax error or access violation: 1118 Row size too large. The maximum row size for the used table type, not counting BLOBs, is 65535. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs 2022-07-15 16:57:54.771 ** ERROR ** For query : CREATE TABLE `issue` ( `id` int(12) unsigned NOT NULL AUTO_INCREMENT, `idProject` int(12) unsigned DEFAULT NULL, `name` varchar(100) DEFAULT NULL, `description` varchar(4000) DEFAULT NULL, `idIssueType` int(12) unsigned DEFAULT NULL, `cause` varchar(4000) DEFAULT NULL, `impact` varchar(4000) DEFAULT NULL, `idPriority` int(12) unsigned DEFAULT NULL, `creationDate` date DEFAULT NULL, `idUser` int(12) unsigned DEFAULT NULL, `idStatus` int(12) unsigned DEFAULT NULL, `idResource` int(12) unsigned DEFAULT NULL, `initialEndDate` date DEFAULT NULL, `actualEndDate` date DEFAULT NULL, `closureDate` date DEFAULT NULL, `result` varchar(4000) DEFAULT NULL, `comment` varchar(4000) DEFAULT NULL, `idle` int(1) unsigned DEFAULT '0', PRIMARY KEY (`id`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE utf8mb4_general_ci ;
Below informations on my Database server :
MariaDB [(none)]> show variables like 'character_set_server' ; +----------------------+---------+ | Variable_name | Value | +----------------------+---------+ | character_set_server | utf8mb4 | +----------------------+---------+ 1 row in set (0.001 sec) MariaDB [(none)]> show variables like 'collation_server' ; +------------------+--------------------+ | Variable_name | Value | +------------------+--------------------+ | collation_server | utf8mb4_general_ci | +------------------+--------------------+ 1 row in set (0.001 sec) MariaDB [(none)]> show databases ; +--------------------+ | Database | +--------------------+ | information_schema | | mysql | | performance_schema | | projeqtor_db | | sys | +--------------------+ 5 rows in set (0.001 sec) MariaDB [(none)]> show create database projeqtor_db ; +--------------+--------------------------------------------------------------------------+ | Database | Create Database | +--------------+--------------------------------------------------------------------------+ | projeqtor_db | CREATE DATABASE `projeqtor_db` /*!40100 DEFAULT CHARACTER SET utf8mb4 */ | +--------------+--------------------------------------------------------------------------+ 1 row in set (0.000 sec) MariaDB [(none)]> SELECT * FROM INFORMATION_SCHEMA.SCHEMATA where SCHEMA_NAME='projeqtor_db' ; +--------------+--------------+----------------------------+------------------------+----------+----------------+ | CATALOG_NAME | SCHEMA_NAME | DEFAULT_CHARACTER_SET_NAME | DEFAULT_COLLATION_NAME | SQL_PATH | SCHEMA_COMMENT | +--------------+--------------+----------------------------+------------------------+----------+----------------+ | def | projeqtor_db | utf8mb4 | utf8mb4_general_ci | NULL | | +--------------+--------------+----------------------------+------------------------+----------+----------------+ MariaDB [(none)]> select version() ; +-------------------------------------+ | version() | +-------------------------------------+ | 10.8.3-MariaDB-1:10.8.3+maria~jammy | +-------------------------------------+ 1 row in set (0.000 sec)
Also, I tried the following and it works without error :
* Create an emtpy database as above
* Deploy Projeqtor v9.5.5 to initialize database schema => no error
* Stop Projeqtor v9.5.5
* Deploy Projeqtor v10.0.1 to update the database => NO ERROR !
Extract of the logs (update to v10.0.1) :
7096 2022-07-15 19:02:47.522 ===== TRACE ===== ===================================== 7097 2022-07-15 19:02:47.522 ===== TRACE ===== 7098 2022-07-15 19:02:47.522 ===== TRACE ===== DataBase actual Version = V9.5.5 7099 2022-07-15 19:02:47.522 ===== TRACE ===== ProjeQtOr actual Version = V10.0.1 7100 2022-07-15 19:02:47.522 ===== TRACE ===== 7101 2022-07-15 19:02:47.522 ===== TRACE ===== DATABASE "projeqtor_db" converted to UTF8MB4 7102 2022-07-15 19:02:47.676 ===== TRACE ===== TABLE "accessprofile" converted to UTF8MB4 7103 2022-07-15 19:02:47.688 ===== TRACE ===== TABLE "accessright" converted to UTF8MB4 7104 2022-07-15 19:02:47.701 ===== TRACE ===== TABLE "accessscope" converted to UTF8MB4 7105 2022-07-15 19:02:47.714 ===== TRACE ===== TABLE "accessscopespecific" converted to UTF8MB4 7106 2022-07-15 19:02:47.765 ===== TRACE ===== TABLE "action" converted to UTF8MB4 7107 2022-07-15 19:02:47.822 ===== TRACE ===== TABLE "activity" converted to UTF8MB4 7108 2022-07-15 19:02:47.835 ===== TRACE ===== TABLE "activityprice" converted to UTF8MB4 7109 2022-07-15 19:02:47.848 ===== TRACE ===== TABLE "activityworkunit" converted to UTF8MB4 7110 2022-07-15 19:02:47.884 ===== TRACE ===== TABLE "affectation" converted to UTF8MB4 7111 2022-07-15 19:02:47.897 ===== TRACE ===== TABLE "alert" converted to UTF8MB4 7112 2022-07-15 19:02:47.913 ===== TRACE ===== TABLE "approvalstatus" converted to UTF8MB4 7113 2022-07-15 19:02:47.926 ===== TRACE ===== TABLE "approver" converted to UTF8MB4 7114 2022-07-15 19:02:47.960 ===== TRACE ===== TABLE "asset" converted to UTF8MB4 7115 2022-07-15 19:02:47.973 ===== TRACE ===== TABLE "assetcategory" converted to UTF8MB4 7116 2022-07-15 19:02:47.987 ===== TRACE ===== TABLE "assignment" converted to UTF8MB4 7117 2022-07-15 19:02:48.000 ===== TRACE ===== TABLE "assignmentrecurring" converted to UTF8MB4 7118 2022-07-15 19:02:48.012 ===== TRACE ===== TABLE "assignmentselection" converted to UTF8MB4 7119 2022-07-15 19:02:48.025 ===== TRACE ===== TABLE "attachment" converted to UTF8MB4 7120 2022-07-15 19:02:48.038 ===== TRACE ===== TABLE "audit" converted to UTF8MB4 7121 2022-07-15 19:02:48.054 ===== TRACE ===== TABLE "auditsummary" converted to UTF8MB4 7122 2022-07-15 19:02:48.067 ===== TRACE ===== TABLE "baseline" converted to UTF8MB4 7123 2022-07-15 19:02:48.120 ===== TRACE ===== TABLE "bill" converted to UTF8MB4 7124 2022-07-15 19:02:48.136 ===== TRACE ===== TABLE "billline" converted to UTF8MB4 7125 2022-07-15 19:02:48.152 ===== TRACE ===== TABLE "brand" converted to UTF8MB4 7126 2022-07-15 19:02:48.191 ===== TRACE ===== TABLE "budget" converted to UTF8MB4 .....
I think issue is not on column size, but on index (MuSql message is not explicit)
Try and change parameter innodb_default_row_format in MySql configuration file (my.ini)
innodb_default_row_format=dynamic
Ok. Thanks. I will try that. But could you provide the link where this is documented?
I answer to myself : this is mentionned here :
Hello,
The value you ask for is the default since MariaDB 10.2.2 ( https://mariadb.com/kb/en/innodb-system-variables/#innodb_default_row_format)
But I still did the test to add this config to my deployment and I have the same errors.
It seems direct install of V10.0 on MySql V5.6 fails.
Try and install V9.5.5, then migrate to V10.0.2
Ticket #6355 recorded
Thanks for the workaround.I already tried it last week (see my previous post).
Yes it works but I'm still very surprised that installing "from scratch" is not one of your first testcases in you CI before releasing a new version.
Came on, hold your horses, really!
I reported this issue and was not complaining at all! We should only give all possible credits to ProjeQtOr team and be greatful for their work an so excellent product as ProjeQtOr is.
As members of Open Source Community, our role is to help with testing and ideas to assist project/product creators and developers in their effort not to complain at all.
Be constructive not desctructive!
I just installed fresh ProjeQtOr from version 10.0.3 zip and can confirm it installed without any issues. Complete new database was created correctly.
Problem solved!
Thanks a lot ProjeQtOr team!