| QUOTE (Kai Team @ August 28, 2013 06:15 am) |
| RE: RESYNC, I didn't add RESYNC (although I properly should have) because we are only updating the user sort or a custom field and I don't believe there are any internal dependencies associated with these fields (famous last words). In consulting with Clyde re: the recalculation of smart names, he said (assuming I had used a RESYNC): |
Yes, it is the RESYNC command that causes the smart names to recalculate.
So why was this happening before the RESYNC command was put in the macro?
I don't recall when (and I don't even remember doing it Image may be NSFW.
Clik here to view.
), but in the code we check to see if you have done a direct sqlite update on the caches table. If so, then at the end of the macro we also check to see if you have run a resync command - if not then we automatically run one for you.Does this mean you never really need to use the RESYNC command in a macro?
Absolutely not! This bit of code is just a safety net to make sure that your database is kept in sync after a direct sqlite update. However, when writing a macro there may be lines of code after the direct sqlite update that need correct "syncing" of GSAK to yield the correct results. So usually it is a good idea to issue the RESYNC command directly after the sqlite command that does the direct update (as always there are exceptions).
