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
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
I guess I was not clear enough. My apologies. dsrt is my own code. I
remember an earlier posting on this list recommended 'go install'
instead of 'go build'
~/go/src/dsrt/dsrt.go, util_linux.go, util_windows.go
And I have written other small programs in go that I use for myself. I
put it
What was the last version of Go which worked for you?
"dsrt" isn't a valid module path in the new module resolution code. Does it
work if you disable modules - "GO111MODULE=off go install dsrt"?
On Sun, Sep 22, 2019 at 9:56 AM rob wrote:
> Hi. I think I'm having an issue compiling my code
nice
On Wednesday, September 25, 2019 at 5:18:51 PM UTC+3, Denis Bakhtin wrote:
>
> This extension works well if templates have .gohtml extension. I had to
> rename mine.
>
> On Monday, September 23, 2019 at 7:25:52 PM UTC+4, cinem...@gmail.com
> wrote:
>>
>> Is there way to highlight templates
I'm getting the sense that my question is below getting an answer I can
understand and follow.
Is there a more suitable site for me to post my question without irritating
people?
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To
"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
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
Let me answer that with code
ORM syntax
db.Where("name = ?", "donald").First()
another ORM syntax
err := o.QueryTable("user").Filter("name", "slene").One()
another ORM syntax
findByUserdAndOrderCreatedAtBetween(String ovoId, Date startDate, Date
endDate, Pageable pgRequest)
does you know
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
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
11 matches
Mail list logo
