13341 2019-05-08 19:05:34 +0000 Fields in orm_layer too small for URLs 2023-07-27 09:17:24 +0000 1 1 7 Build System, Metadata & Runtime Toaster toaster 0.0.0 x86 Multiple RESOLVED WORKSFORME Medium normal 4.3 M2 1 jgorkos david.reyna jessica.zhang randy.macleod stanciux.mihail toaster --- --- Don't know oldest_to_newest 83741 0 jgorkos 2019-05-08 19:05:34 +0000 While installing Toaster "from scratch", during the 'checksettings' phase of the installation manual at step 6 of section 3.9.2, I'm seeing "data too long for column vcs_web_tree_base_url" errors during database population. After altering the database fields in orm_layer from varchar(200) to varchar(400), I see this: MariaDB [toaster_data]> select max(length(vcs_web_tree_base_url)) from orm_layer; +------------------------------------+ | max(length(vcs_web_tree_base_url)) | +------------------------------------+ | 205 | +------------------------------------+ 1 row in set (0.001 sec) MariaDB [toaster_data]> select max(length(vcs_web_file_base_url)) from orm_layer; +------------------------------------+ | max(length(vcs_web_file_base_url)) | +------------------------------------+ | 205 | +------------------------------------+ 1 row in set (0.001 sec) I'm also seeing other instances of columns being too small for the data: Updating recipes 13%2019-05-08 10:55:18,691 WARNING Failed saving recipe (1406, "Data too long for column 'license' at row 1") That appears to be in table orm_recipe, where license is varchar(200). I'm wondering if just declaring these as "text" or "varchar" of undefined length would be a quick solution. 96117 1 david.reyna 2023-07-27 09:17:24 +0000 Per Kieran McNulty (WInd River) "I can set up a production instance without raising the error. Used mysql. Although the checksettings command that is supposed to raise an error gives no output, which is suspicious, I can continue with the setup process fine." David