And I’ll reiterate that you’re (and the article) is missing the point.
Using a simple case of customers and orders. With an ORM when you want to show all orders for all customers with the customer details, you need to join the customer with the order in every row. This is a huge waste of bandwidth (although many advanced db drivers won’t ship the redundant customer info over the network). So either you use an ORM or you roll your own (using maps and lookups). And this is just a trivial 2 table join. > On Sep 27, 2019, at 7:05 AM, Lutz Horn <lutz.h...@posteo.de> wrote: > >> On Fri, Sep 27, 2019 at 05:34:28PM +0700, Dimas Prawira wrote: >> Many Gophers don't like ORM as : > > Just to emphasize this point: > > https://korban.net/posts/postgres/2017-11-02-the-case-against-orms/ > > Lutz > > -- > 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/20190927120547.GA4127%40pc-lutz.ecm4u.intra. -- 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/D5892013-0777-49E2-AC31-0A643D8D0A8D%40ix.netcom.com.
