Re: [go-nuts] Re: Do you guys use ORMs when working with SQL?

2017-09-11 Thread Simon Ritchie
> Why would someone want to switch from PostgreSQL to MySQL? It's fairly common to use one database for production and another (often in memory) for testing, with an ORM hiding the differences. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group.

Re: [go-nuts] Re: Do you guys use ORMs when working with SQL?

2017-09-10 Thread Henrik Johansson
The switching of databases can happen but I have always solved it at a higher "service" level. What ORM's help you with is quickly getting started and it can in some cases help you with type safety. In the (not so) long run only the second matter and personally I wish there was something like

Re: [go-nuts] Re: Do you guys use ORMs when working with SQL?

2017-09-10 Thread Shawn Milochik
On Sun, Sep 10, 2017 at 11:31 AM, wrote: > Modern ORMs at least more type-safe than SQL: there is no work with > strings, only with autogenerated constants. Also ORMs abstract you not only > from SQL coding, but also from specific for DBMS SQL: with ORM you can > easily

Re: [go-nuts] Re: Do you guys use ORMs when working with SQL?

2017-09-10 Thread main . iden
Modern ORMs at least more type-safe than SQL: there is no work with strings, only with autogenerated constants. Also ORMs abstract you not only from SQL coding, but also from specific for DBMS SQL: with ORM you can easily switch PostgreSQL to MySQL. воскресенье, 10 сентября 2017 г., 3:43:42

Re: [go-nuts] Re: Do you guys use ORMs when working with SQL?

2017-09-09 Thread Shawn Milochik
In my opinion, ORMs are worse than useless. You need to know SQL to use an ORM. So if you use an ORM, you must bear in mind the underlying SQL *and* know the syntax of the ORM. Using an ORM "saves" you from writing some boilerplate code, but then you have to write ORM-specific boilerplate code,

[go-nuts] Re: Do you guys use ORMs when working with SQL?

2017-09-09 Thread Tim Uckun
Wow. the amazing amount of projects mentioned in this thread are interesting. Surprised that by now there isn't a well established leader or leaders for such a common need. On Sunday, September 10, 2017 at 10:01:51 AM UTC+12, Denis Isaev wrote: > > Take a look at kallax

[go-nuts] Re: Do you guys use ORMs when working with SQL?

2017-09-09 Thread main . iden
Take a look at kallax and queryset . They are modern typesafe ORMs, allowing to write safe and reusable code. среда, 28 декабря 2016 г., 1:00:05 UTC+3 пользователь Zippoxer написал: > > I haven't written SQL for years.

[go-nuts] Re: Do you guys use ORMs when working with SQL?

2016-12-30 Thread mhhcbon
did anyone effectively worked with https://github.com/relops/sqlc ? That s a great property to be able to compile time check the dal. Also i wonder how this, or that approach, could handle true modular integration with extensible schema and dependencies management. -- You received this

[go-nuts] Re: Do you guys use ORMs when working with SQL?

2016-12-30 Thread Henry
On Friday, December 30, 2016 at 7:43:13 PM UTC+7, parais...@gmail.com wrote: > > Go type system makes generalization impossible if you also need type > safety. Not only ORM are complicated but the fact that Go lacks generic > programming features makes a Go ORM API even more horrible to use,

[go-nuts] Re: Do you guys use ORMs when working with SQL?

2016-12-29 Thread a . modzelewski
I far prefer solutions like Squirrel (https://github.com/Masterminds/squirrel) to ORMs for most problems — I still write queries, but use a more convenient syntax. It also means I'm less likely to somehow accidentally introduce an injection vulnerability. Usually that's enough abstraction to

[go-nuts] Re: Do you guys use ORMs when working with SQL?

2016-12-29 Thread Jakub Labath
Hi, When I gave some thought to the whole ORM, I concluded it was not the SQL that bothered me it was these items 1. Adding a new column to table means having to revisit every query/insert/update that could be affected 2. Serializing and de-serializing as things get saved/read from DB (dealing

[go-nuts] Re: Do you guys use ORMs when working with SQL?

2016-12-28 Thread Jon Bodner
I've written a library called Proteus that is a simple tool for dynamically generating a data access layer: https://github.com/jonbodner/proteus You need to write the SQL queries, but it will map values (variables, slices, structs, maps) into queries and map the results into a struct or map.

[go-nuts] Re: Do you guys use ORMs when working with SQL?

2016-12-28 Thread mhhcbon
DBR is a good pick to me. https://github.com/gocraft/dbr It does the little missing from std package. much like previous answer explained it. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving

[go-nuts] Re: Do you guys use ORMs when working with SQL?

2016-12-28 Thread John Jeffery
There are many good ORMs for Go. One good list can be found at https://awesome-go.com/#orm I think ORMs definitely have their place, and I have made good use of NHibernate in the .NET environment and Hibernate in Java. Having said that, I have found that for almost all of the work I have done