custom data insert/update error if using reserved words
Ran into a situation where a client had created a custom field titled "use", which resulted in a column in the corresponding value table with that name. Because it is a reserved word, it triggered errors during insert/update. This is easily remedied with the use of backticks (which we're starting to use more consistently anyway).
One could argue we should address this upstream and prevent the creation of fields with reserved names. But that won't address previously created fields, and adding backticks to our SQL is a good policy anyway.