| QUOTE (Kai Team @ July 24, 2013 06:50 am) | ||
As a fairly prolific macro author, I don't see the value of doing that. The trigger for this issue is updating the database, which could be done with $d_DBVariable=X, or it could be done with a direct SQLite update (UPDATE CACHES SET DBVariable=X). There is also some judgement involved in where you place the TRANSACTION, depending on how the code is structured, both to get maximum efficiency and to avoid the problems that lead to Clyde removing the automatic Transactions (e.g. attempting certain actions in the middle of a transaction). Can you clarify why you think it would be useful to identify the variable(s) causing the warning? |
...and you can always fix the problem by adding a TRANSACTION around the entire macro as GSAK used to do. It may not be the most efficient position, but it will work.