> The golang one uses a word ("value") for a field name that's been a reserved word since SQL-1999. It will work in popular open source SQL databases, but I bel

> The golang one uses a word ("value") for a field name that's been a reserved word since SQL-1999. It will work in popular open source SQL databases, but I believe it would bomb in some servers if not delimited...which it is not. In their defense they created the table with this column before invoking the autocomplete, so they sort of reap what the sow here. It could at least auto-quote the column names to remove the ambiguity, but it's not a compiler, is it.