@[deleted]
Well you actually can NOT roll-back MySQL version, so you are literally stuck.
We're on AWS, so what we did:
1) started new RDS DB server instance using old MYQL 5.7
2) restored a snapshot to the 5.7 version
3) connected AwareIM to the v5.7 database
3) adjusted all reserved words attributes in AwareIM config and stored procedures too
4) published all the BSVs affected
5) proceed with update of MySQL to V8
@[deleted]
yes you can't have a column name as a reserved word, so we're talking Business Object attribute names
the BIG issue you have is that you might update MySQL and not even be aware about this issue for a year or more (in our case)... if it is a little used attribute, it just sits dormant for a while but then a process runs or a query using that attribute and you get a MySQL error THEN you can't fix it, because you can't publish (and change the attribute name) because on going into test you get a MySQL error... you're now stuck, one way, dead end street - AwareIM won't let you delete the attribute, nor change it's name as it requires it to run a SQL statement using a reserved word - fun huh
