I haven't written SQL for years. I was enjoying MongoDB with the awesome
mgo package, and what saved me a lot of headache was the natural
programmatic interface of MongoDB.
mgo maps your data (structs, maps, slices) to MongoDB queries and from
MongoDB results, and you can write any MongoDB query
I use plain SQL. Since I deal with mostly financial data, I need to control how
my data get changed. I don't want some ORMs doing some funky business which may
inadvertently lead to data corruption. I usually write a mapper for every table
in the database. If a table structure is changed, I just
> Why would someone want to switch from PostgreSQL to MySQL?
I recently switched a project from PostgreSQL to MySQL. But I sure can’t say I
*wanted* to. We were integrating a dependency that only supports MS SQL Server
and MySQL.
--
You received this message because you are subscribed to the G
On Dec 30, 2016, at 4:43 AM, paraiso.m...@gmail.com wrote:
>
> Ultimately even if you stick to SQL you are just also writing your own ORM ,
> you just can't generalize code because of Go type system.
There are really two separate (but related) issues in the ORM debate: the ORM
design pattern, a
