You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Next on the STRICT_TRANS_TABLES fallout is sections.migrated_time. It's preventing us from creating a new project from a project code because there is no default value.
We're not really sure what sections.migrated_time is for or where it came from. It looks to be intended as a duration, but it's filled with invalid values and other garbage. Its only reference in the code is in the RSS view application/views/rss/rss.php. We want to give it a default value of NULL, and in the process, let's clean it up and make it a proper TIME column.
altertable sections modify column migrated_time varchar(20) null;
update sections set migrated_time =NULLwhere migrated_time ='Source:';
update sections set migrated_time =substring(migrated_time,1,8) where migrated_time like"%Source:";
update sections set migrated_time =NULLwhere length(migrated_time) >8;
update sections set migrated_time =NULLwhere migrated_time like'%Sung%';
update sections set migrated_time =NULLwhere migrated_time ='';
update sections set migrated_time =NULLwhere migrated_time like'%by%';
update sections set migrated_time ='00:15:07'where migrated_time ='00:15"07';
update sections set migrated_time ='01:13:50'where id =126048;
update sections set migrated_time =NULLwhere id =163744;
update sections set migrated_time =NULLwhere migrated_time like'1599%';
update sections set migrated_time =NULLwhere migrated_time like'Book%';
altertable sections modify column migrated_time timenull;
The text was updated successfully, but these errors were encountered:
With the move to Jammy, MariaDB now has STRICT_TRANS_TABLES on by
default. This means we can no longer do things like save empty strings
into integer columns and have them magically transformed into the
correct type (which I assume is what was happening before). This patch
adds a bunch of code around places where such slopiness was detected
during testing. The patch is half of the fix, the other half is
issues LibriVox#147 and LibriVox#148.
notartom
added a commit
to notartom/librivox-catalog
that referenced
this issue
Dec 2, 2022
With the move to Jammy, MariaDB now has STRICT_TRANS_TABLES on by
default. This means we can no longer do things like save empty strings
into integer columns and have them magically transformed into the
correct type (which I assume is what was happening before). This patch
adds a bunch of code around places where such slopiness was detected
during testing. The patch is half of the fix, the other half is
issues LibriVox#147 and LibriVox#148.
With the move to Jammy, MariaDB now has STRICT_TRANS_TABLES on by
default. This means we can no longer do things like save empty strings
into integer columns and have them magically transformed into the
correct type (which I assume is what was happening before). This patch
adds a bunch of code around places where such slopiness was detected
during testing. The patch is half of the fix, the other half is
issues #147 and #148.
Next on the STRICT_TRANS_TABLES fallout is
sections.migrated_time
. It's preventing us from creating a new project from a project code because there is no default value.We're not really sure what
sections.migrated_time
is for or where it came from. It looks to be intended as a duration, but it's filled with invalid values and other garbage. Its only reference in the code is in the RSS viewapplication/views/rss/rss.php
. We want to give it a default value of NULL, and in the process, let's clean it up and make it a properTIME
column.The text was updated successfully, but these errors were encountered: