Just out of curiosity - why switch away from gorm?? We've just switched from gorp to gorm - with great success. The main reason I could find for going (pun intended) is to have one less dependency.
-- Michael Banzon https://michaelbanzon.com/ Den 20. jul. 2017 kl. 06.04 skrev Nate Finch <nate.fi...@gmail.com>: We're thinking of dropping gorm and switching to plain old database/sql... but I don't really want to generate all that boilerplate myself. xo looks like it does a reasonable job of generating the boilerplate for you, so I was wondering if anyone had any experience using it in production. Gotchas, etc. -Nate -- 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. For more options, visit https://groups.google.com/d/optout. -- 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. For more options, visit https://groups.google.com/d/optout.
