Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I don’t have specific experience with
go-psql, but since there’s no answer I’ll write my thoughts.There are issues with the current implementation, which might bite you (e.g. time resolution lower than seconds is ignored. What happens if you update a single field, but your
ORMdecides to include atimefield within the query?).Other problem that I see is, there’s no promise this project will be maintained as long as you wish.
Another approach is to build a very simple binding to the
postgresC interface, and just use it. In that case, the abstraction is not very helpful, but definitely not leaky. And it might be enough.That’s what Russ Cox (from the core Go (golang) team) ended up doing for sqlite.