You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Other than a couple of passing references in column.go and doc.go, it's not clear that sqlbuilder is meant to be run against mysql. Postgres barfs at least on the backticks for quoting. I have not tested it against sqlite.
It would be good to make this very clear in the package docs and README at a minimum. Do you have plans or want to support additional SQL flavors in the future?
The text was updated successfully, but these errors were encountered:
We are running thousands of mysql boxes in production. It's unlikely that we'll switch to other sql variant at this point (except maybe webscale).
I'll update the document to clarify that sqlbuilder currently only works for mysql.
You're welcome to submit a patch to support other sql flavors. Perhaps add SerializeSqlWithOptions(buffer, options) to the Clause interface and override the default behavior for column serialization.
Other than a couple of passing references in column.go and doc.go, it's not clear that sqlbuilder is meant to be run against mysql. Postgres barfs at least on the backticks for quoting. I have not tested it against sqlite.
It would be good to make this very clear in the package docs and README at a minimum. Do you have plans or want to support additional SQL flavors in the future?
The text was updated successfully, but these errors were encountered: