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
I noticed the following in thold database.php function thold_setup_database() that it changes the base application table settings, column "value" size to 4096.
/* increase the size of the settings table */
db_execute("ALTER TABLE settings
MODIFY COLUMN `value`
varchar(4096) NOT NULL default ''");
I wonder if that is for values thold_down_text and thold_up_text.
In running the base application database repair for troubleshooting other, one repair was the settings table column value size from 4096 to 2048.
Checking Table: 'settings'
ERROR Col: 'value', Attribute 'Type' invalid. Should be: 'varchar(2048)', Is: 'varchar(4096)'
I thought I would to mention it in case it could be a potential data loss that should be noted somewhere if not already.
The text was updated successfully, but these errors were encountered:
TheWitness
changed the title
Settings table custum size reverted by database repair
Settings table custmm size reverted by database repair
Nov 16, 2023
TheWitness
changed the title
Settings table custmm size reverted by database repair
Settings table custom size reverted by database repair
Nov 16, 2023
netniV
changed the title
Settings table custom size reverted by database repair
Settings table updates for large values reverted by database repair
Dec 16, 2023
I noticed the following in thold database.php function thold_setup_database() that it changes the base application table settings, column "value" size to 4096.
I wonder if that is for values thold_down_text and thold_up_text.
In running the base application database repair for troubleshooting other, one repair was the settings table column value size from 4096 to 2048.
I thought I would to mention it in case it could be a potential data loss that should be noted somewhere if not already.
The text was updated successfully, but these errors were encountered: