If you periodically "patch" some column of a table, then the columns will have the wrong data for some time. You probably don't want that.
Instead, I think a trigger will be better, since it will "fix" the data on the fly while being inserted/updated. The table won't ever have the wrong data to begin with.
See 24.3.1 Trigger Syntax and Examples.
For example (tweak as necessary):
create table users (id int, bouquet varchar(100));
create trigger fix_data before insert on users
for each row
begin
set NEW.bouquet = '["12","10","11","8","9","6","7","5","4","3","2","1"]';
end;
Then, if you run the following INSERT
statements:
insert into users (id, bouquet) values (1, 'Hello');
insert into users (id) values (2);
insert into users (id, bouquet) values (3, null);
insert into users (id, bouquet) values (4,
'["12","10","11","8","9","6","7","5","4","3","2","1"]');
select * from users;
You get the result:
id bouquet
-- ----------------------------------------------------
1 ["12","10","11","8","9","6","7","5","4","3","2","1"]
2 ["12","10","11","8","9","6","7","5","4","3","2","1"]
3 ["12","10","11","8","9","6","7","5","4","3","2","1"]
4 ["12","10","11","8","9","6","7","5","4","3","2","1"]