alex.besogo...@gmail.com:
But the main issue is that Go SQL interface SUCKS. It's verbose, hard to use and is difficult to integrate with additional tooling (try adding generic tracing support, I dare you!). So often your SQL code is hidden in reams of wrapper code that sets arguments and reads the results.
That's true. In the Java world, few people use the JDBC API directly, which has similar flaws. But this does not mean that JPA and Hibernate have to be used. Libraries like JDBI[1] exist that provide a much more usable API without the necessities of the ORM concept.
Ragarding the "migration" part of the question, in the Java world libraries like Flyway[2] allow fine grained control of schema migrations.
For both use cases similar libraires surely exist for Go. But maybe the question was about migrating ORM code and the DB schema together. I am not aware of any solution that does this.
Lutz [1] http://jdbi.org/ [2] https://flywaydb.org/ -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/0aab4dd2-374b-1915-b6f7-77089c42733f%40posteo.de.
