On Mon, Sep 30, 2019, at 21:05, bram wrote:
> Thank you all. For schema migration i am looking for similar tool
> like flyway.
I'm not sure if it's like flyway, but I use a library that I wrote,
code.soquee.net/migration [1]. The idea is that it gives you the tools
you need to write a migration co
I created a simple migration tool called mgrt [1], which operates on pure SQL
scripts that are defined by the user. It has support for MySQL, SQLite and
PostgreSQL. Give it a try if you're looking for a simple migration tool that
just uses plain SQL under the hood. It's written in Go, so building i
Thank you all. For schema migration i am looking for similar tool like
flyway.
,
Regards,
Bram.
On Sunday, September 29, 2019 at 2:34:55 AM UTC-7, Space A. wrote:
>
> ORM is a tool. It's not good or bad. Every tool, every language and
> everything has limits. If you like spending time on writ
ORM is a tool. It's not good or bad. Every tool, every language and
everything has limits. If you like spending time on writing and debugging
raw SQL - go ahead. The difference and very obvious in this discussion, is
that those who are not against ORM not trying to convince other party to
only use
I've used naked SQL, and ORMs (Django in Python, Hibernate and EBean in
Java, GORM in Go) for years, and I've noticed the following:
1) It's really easy to write very inefficient queries in an ORM. If you
have a very simple 1:1 mapping between tables and objects, it's fast,
efficient, easy to use,
ORM is object relational mapping. Go is only pseudo object oriented. I will say
again that complex object graphs and persistence is very hard without an ORM or
a LOT of custom code.
Since Go does not have runtime compilation a true (or easy anyway) ORM in Go
requires code generation.
> On Se
"First, nobody thinks that knowing ORM's query language absolves one from
knowing SQL."
Speak for yourself.
If you a hard spring boot user you can get into this problem.
Example:
findAll = select * from entity
This is have nothing with SQL.
findAllBySomeProperty = select * from entity where p
migrations should not be _rarely_ if you are writing migration scripts
often, that's a big big big big different problem
cheers
On Sat, Sep 28, 2019 at 8:03 PM Lutz Horn wrote:
> alex.besogo...@gmail.com:
> > But the main issue is that Go SQL interface SUCKS. It's verbose, hard to
> > use and i
Let me answer that with code
ORM syntax
db.Where("name = ?", "donald").First(&user)
another ORM syntax
err := o.QueryTable("user").Filter("name", "slene").One(&user)
another ORM syntax
findByUserdAndOrderCreatedAtBetween(String ovoId, Date startDate, Date
endDate, Pageable pgRequest)
does y
alex.besogo...@gmail.com:
But the main issue is that Go SQL interface SUCKS. It's verbose, hard to
use and is difficult to integrate with additional tooling (try adding
generic tracing support, I dare you!). So often your SQL code is hidden
in reams of wrapper code that sets arguments and reads
Absolutely, plus ORM usually offers a convenient way to run raw SQL
queries, if you need it.
On Saturday, September 28, 2019 at 7:50:22 AM UTC+3, alex.b...@gmail.com
wrote:
>
> First, nobody thinks that knowing ORM's query language absolves one from
> knowing SQL.
>
> But the main issue is th
First, nobody thinks that knowing ORM's query language absolves one from
knowing SQL.
But the main issue is that Go SQL interface SUCKS. It's verbose, hard to
use and is difficult to integrate with additional tooling (try adding
generic tracing support, I dare you!). So often your SQL code is h
It was supposed to be “without an ORM”...
> On Sep 27, 2019, at 1:27 PM, Robert Engels wrote:
>
> 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 c
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 bandwi
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" g
This works well for me.
https://upper.io/db.v3/
On Fri, 27 Sep 2019 at 15:56, Robert Engels wrote:
> The piece you are missing about ORM is the automatic change detection and
> caching when using complex object graphs. This is not trivial by any means
> when using raw SQL. It’s not easy using an
The piece you are missing about ORM is the automatic change detection and
caching when using complex object graphs. This is not trivial by any means when
using raw SQL. It’s not easy using an orm either sometimes - depends on the
orm.
> On Sep 27, 2019, at 6:13 AM, Dimas Prawira
> wrote:
>
if there's something you _don't_ know how to do in SQL, and it seems the
ORM can do it for you, capture the raw SQL the ORM produces
and tell me if it's easier for you to understand the SQL or the random ORM
API. I 100% guarantee you that the raw SQL the ORM produces will be easier
to understand
i
Many gophers like ORM.
ORM is a tool and as any other tool it does save the time when used in a
right way in a right place. But you need to learn how to use it.
пт, 27 сент. 2019 г. в 13:35, Dimas Prawira :
> Many Gophers don't like ORM as :
> 1. ORM introduce an additional layer of abstraction
Many Gophers don't like ORM as :
1. ORM introduce an additional layer of abstraction that doesn't accomplish
anything.
2. SQL syntax is more or less the same for every database.
3. If you learn an ORM in Java, you will only ever able to use that ORM
knowledge in Java. If you learn SQL, you can use
Hi,
Can you pls suggest libs for ORM & Schema Migration.
Thanks.
--
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 v
21 matches
Mail list logo
