We use it, but due to working with a legacy schema we've had to make
some internal changes to it to ensure we get decent go structures.
You can see the sort of things we've really quickly hacked into it, not
had time to upstream, here:
https://github.com/stevenh/xo/commits/mysql-primary-keys
Key ones include:
* Multiple column primary keys for MySQL.
* Small and tiny for MySQL.
* Field tags for autoinc, default and primary key.
* Escape support for MySQL.
* Remapping support.
We also use a custom set of templates.
Its a sound library and covers the basics but we still end up rolling a
lot of had written SQL.
Regards
Steve
On 20/07/2017 05:04, Nate Finch wrote:
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
<mailto: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.
