Unable to create URL field in Call Entity

[Athensmusic]

HI there,
we are not able to create any URL field type in Call entity.
We get an "Error 500: Error while rebuilding database. See log file for details."
We are able to rebuild from admin panel and cli too.
Any help?

Log:
[2021-11-24 07:22:28] ALERT: Rebuild database fault: PDOException: 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 in /home/hidden_for_security/espo/vendor/doctrine/dbal/src/Driver/PDO/Connection.php:82 Stack trace: #0 /home/hidden_for_security/espo/vendor/doctrine/dbal/src/Driver/PDO/Connection.php(82): PDO->query('ALTER TABLE `ca...') #1 /home/hidden_for_security/espo/vendor/doctrine/dbal/src/Connection.php(1035): Doctrine\DBAL\Driver\PDO\Connection->query('ALTER TABLE `ca...') #2 /home/hidden_for_security/espo/application/Espo/Core/Utils/Database/Schema/Schema.php(231): Doctrine\DBAL\Connection->executeQuery('ALTER TABLE `ca...') #3 /home/hidden_for_security/espo/application/Espo/Core/Utils/Database/Schema/SchemaProxy.php(53): Espo\Core\Utils\Database\Schema\Schema->rebuild() #4 /home/hidden_for_security/espo/application/Espo/Core/DataManager.php(146): Espo\Core\Utils\Database\Schema\SchemaProxy->rebuild(Array) #5 /home/hidden_for_security/espo/application/Espo/Core/DataManager.php(115): Espo\Core\DataManager->rebuildDatabase(Array) #6 /home/hidden_for_security/espo/application/Espo/Controllers/FieldManager.php(103): Espo\Core\DataManager->rebuild(Array) #7 /home/hidden_for_security/espo/application/Espo/Core/Api/ActionProcessor.php(95): Espo\Controllers\FieldManager->postActionCreate(Object(Espo\Core\Api\RequestWr ap per), Object(Espo\Core\Api\ResponseWrapper)) #8 /home/hidden_for_security/espo/application/Espo/Core/Api/RequestProcessor.php(136): Espo\Core\Api\ActionProcessor->process('FieldManager', 'create', Object(Espo\Core\Api\RequestWrapper), Object(Espo\Core\Api\ResponseWrapper)) #9 /home/hidden_for_security/espo/application/Espo/Core/Api/RequestProcessor.php(111): Espo\Core\Api\RequestProcessor->proceed(Object(Espo\Core\Api\RequestWrapper), Object(Espo\Core\Api\ResponseWrapper)) #10 /home/hidden_for_security/espo/application/Espo/Core/Api/RequestProcessor.php(82): Espo\Core\Api\RequestProcessor->processInternal(Object(Espo\Core\Api\Route), Object(Espo\Core\Api\RequestWrapper), Object(Espo\Core\Api\ResponseWrapper)) #11 /home/hidden_for_security/espo/application/Espo/Core/Api/Starter.php(103): Espo\Core\Api\RequestProcessor->process(Object(Espo\Core\Api\Route), Object(Espo\Core\Api\RequestWrapper), Object(Espo\Core\Api\ResponseWrapper)) #12 /home/hidden_for_security/espo/vendor/slim/slim/Slim/Handlers/Strategies/RequestResponse.php(43): Espo\Core\Api\Starter->Espo\Core\Api\{closure}(Object(Slim\Psr7\Reques t) , Object(Slim\Psr7\Response), Array) #13 /home/hidden_for_security/espo/vendor/slim/slim/Slim/Routing/Route.php(384): Slim\Handlers\Strategies\RequestResponse->__invoke(Object(Closure), Object(Slim\Psr7\Request), Object(Slim\Psr7\Response), Array) #14 /home/hidden_for_security/espo/vendor/slim/slim/Slim/MiddlewareDispatcher.php(81): Slim\Routing\Route->handle(Object(Slim\Psr7\Request)) #15 /home/hidden_for_security/espo/vendor/slim/slim/Slim/MiddlewareDispatcher.php(81): Slim\MiddlewareDispatcher->handle(Object(Slim\Psr7\Request)) #16 /home/hidden_for_security/espo/vendor/slim/slim/Slim/Routing/Route.php(341): Slim\MiddlewareDispatcher->handle(Object(Slim\Psr7\Request)) #17 /home/hidden_for_security/espo/vendor/slim/slim/Slim/Routing/RouteRunner.php(84): Slim\Routing\Route->run(Object(Slim\Psr7\Request)) #18 /home/hidden_for_security/espo/vendor/slim/slim/Slim/Middleware/RoutingMiddleware.php(59): Slim\Routing\RouteRunner->handle(Object(Slim\Psr7\Request)) #19 /home/hidden_for_security/espo/vendor/slim/slim/Slim/MiddlewareDispatcher.php(147): Slim\Middleware\RoutingMiddleware->process(Object(Slim\Psr7\Request), Object(Slim\Routing\RouteRunner)) #20 /home/hidden_for_security/espo/vendor/slim/slim/Slim/Middleware/ErrorMiddleware.php(107): class@anonymous->handle(Object(Slim\Psr7\Request)) #21 /home/hidden_for_security/espo/vendor/slim/slim/Slim/MiddlewareDispatcher.php(147): Slim\Middleware\ErrorMiddleware->process(Object(Slim\Psr7\Request), Object(class@anonymous)) #22 /home/hidden_for_security/espo/vendor/slim/slim/Slim/MiddlewareDispatcher.php(81): class@anonymous->handle(Object(Slim\Psr7\Request)) #23 /home/hidden_for_security/espo/vendor/slim/slim/Slim/App.php(215): Slim\MiddlewareDispatcher->handle(Object(Slim\Psr7\Request)) #24 /home/hidden_for_security/espo/vendor/slim/slim/Slim/App.php(199): Slim\App->handle(Object(Slim\Psr7\Request)) #25 /home/hidden_for_security/espo/application/Espo/Core/Api/Starter.php(79): Slim\App->run() #26 /home/hidden_for_security/espo/application/Espo/Core/ApplicationRunners/Api.php(49): Espo\Core\Api\Starter->start() #27 /home/hidden_for_security/espo/application/Espo/Core/Application/RunnerRunner.php(85): Espo\Core\ApplicationRunners\Api->run() #28 /home/hidden_for_security/espo/application/Espo/Core/Application.php(78): Espo\Core\Application\RunnerRunner->run('Espo\\Core\\Appli...', NULL) #29 /home/hidden_for_security/espo/public/api/v1/index.php(37): Espo\Core\Application->run('Espo\\Core\\Appli...') #30 {main... [] [] [2021-11-24 07:22:28] ERROR: (500) Error while rebuilding database. See log file for details.; POST /Admin/fieldManager/Call; line: 108, file: /home/hidden_for_security/espo/application/Espo/Controllers/FieldManager.php [] []

[Kyle]

This is a MYSQL limit you have to many columns that exceed the max storage size of the DB.

Some solutions:
1) if you have columns you have created but later removed they are in the DB still, delete the columns you do not need.
2) Adjust the size of your varchar and enum fields, this needs to be done in the metadata and then you will manually need to adjust the DB fields.

[Athensmusic]

Thanks for replying Kyle,
we just started a new entity with double quantity fields without any issue, so probably -i guess because of tests we made- your first option caused this problem.
Fortunately was an empty entity without any data loss.