Bug #13222

Build SQL task changes the size of culture columns

Added by José Raddaoui Marín 3 months ago. Updated about 1 month ago.

Status:VerifiedStart date:12/05/2019
Priority:LowDue date:
Assignee:-% Done:

0%

Category:Data model / ORM
Target version:Release 2.6.0
Google Code Legacy ID: Tested version:2.5, 2.6
Sponsored:No Requires documentation:

Description

Each time a change is introduced in the models schema (YML file) the following tasks have to be executed to generate the database schema (SQL file) used on the install process to create the AtoM datase and the base model classes.

php symfony propel:build-sql
php symfony propel:build-model

On #9051, the size of the culture columns was increased from 7 to 16 chars directly on the SQL schema (related commit), which causes its modification back to 7 chars each time the build-sql task is executed.

Additionally, this columns are added automatically by Symfony based on the _i18n tables, so changing it's size may cause other issues. For example, the languages form on the settings page validates the culture selected internally with this function, which validates the culture value using a regular expression and also looks for a data file on this folder. So, to be fair, I don't really know how the "ca@valencia" culture even works.


Related issues

Related to Access to Memory (AtoM) - Bug #9051: AtoM breaks with STRICT_TRANS_TABLES Verified 10/13/2015
Related to Access to Memory (AtoM) - Bug #13181: Languages with 3-letter codes cannot be added in AtoM's u... In progress 09/24/2019

History

#1 Updated by Mike Cantelon about 1 month ago

  • Related to Bug #9051: AtoM breaks with STRICT_TRANS_TABLES added

#2 Updated by Mike Cantelon about 1 month ago

  • Related to Bug #13181: Languages with 3-letter codes cannot be added in AtoM's user interface settings added

#3 Updated by Mike Cantelon about 1 month ago

Build SQL column size issue should now be fixed, but issues in the final paragraph likely remain.

#4 Updated by José Raddaoui Marín about 1 month ago

  • Status changed from New to Verified
  • Target version set to Release 2.6.0

Thanks Mike, I can verify this one and we could use #13181 to follow-up about the culture validation.

Also available in: Atom PDF