Live data from Hacker News

Open-sourcing SQX, a way to build flexible database models in Go

stytch.com

11–20 of 28 posts

Re: Open-sourcing SQX, a way to build flexible database models in Go

#11

Earlier quoted context omitted.

It's easy to drop down to pure SQL in every ORM I've ever used. Meanwhile, a good ORM gives you type safe queries, and saves from having to write boilerplate for trivial CRUD. I honestly would like to know which ORMs most critics have experience with. If it's something terrible like Hibernate, then no wonder. For reference, the ORM I've used the most is Entity Framework (the new one, rewritten for NET Core), and it's…

Type safe sql is a feature of most every production quality db library I’ve used going back 20 years. You don’t need the complexity of an orm to get that. As for trivial boilerplate, I tend to find that trivial boilerplate no more troubling than any of the other compromises orms require, whether that’s polluting my data model with sql concerns or making me conform to db practices that aren’t correct for my needs. And…

I still find myself having the experience of having to unit test trivialities with direct SQL coding, lest I miss a typo, which is a (very basic) thing any ORM or query wrapper will tend to save me from.

Re: Open-sourcing SQX, a way to build flexible database models in Go

#12
post #6

This does look like it's a little bit better than a lot of the other options in the Go ecosystem for database access, but this introduction misses something important: what SQL dialects does this support? It appears to be partly a wrapper around Squirrel. Squirrel is not new (and apparently also no longer being updated) but I actually have no idea which and how much of each SQL dialect Squirrel supports. Every time I…

SQLc is amazing, I think it should be the gold standard for SQL in Go

Re: Open-sourcing SQX, a way to build flexible database models in Go

#14

This looks interesting. The only db libraries I can stand are sql query builders. I have experienced way too much pain with orms over the years. They work until you have to do anything slightly complicated and they either get very difficult to use or very slow

It's easy to drop down to pure SQL in every ORM I've ever used. Meanwhile, a good ORM gives you type safe queries, and saves from having to write boilerplate for trivial CRUD. I honestly would like to know which ORMs most critics have experience with. If it's something terrible like Hibernate, then no wonder. For reference, the ORM I've used the most is Entity Framework (the new one, rewritten for NET Core), and it's…

Yes ORM let me write plain SQL. But most time I find painful is the session management inside ORM. When does it decides to flush the query, and how it terminates an idle connection. In async mode, how does it add locks? When I try to customize the connection pool, and then all pain drives me away from ORM.

Re: Open-sourcing SQX, a way to build flexible database models in Go

#15
post #7

We are really happy using jet. It lets you write type safe SQL and can read the results into structs- including joins into slice fields. https://github.com/go-jet/jet

The best SQL query builder for Golang. Used it in 4 projects in production.

Re: Open-sourcing SQX, a way to build flexible database models in Go

#16
post #6

This does look like it's a little bit better than a lot of the other options in the Go ecosystem for database access, but this introduction misses something important: what SQL dialects does this support? It appears to be partly a wrapper around Squirrel. Squirrel is not new (and apparently also no longer being updated) but I actually have no idea which and how much of each SQL dialect Squirrel supports. Every time I…

[deleted]

Re: Open-sourcing SQX, a way to build flexible database models in Go

#18

This looks interesting. The only db libraries I can stand are sql query builders. I have experienced way too much pain with orms over the years. They work until you have to do anything slightly complicated and they either get very difficult to use or very slow

It's easy to drop down to pure SQL in every ORM I've ever used. Meanwhile, a good ORM gives you type safe queries, and saves from having to write boilerplate for trivial CRUD. I honestly would like to know which ORMs most critics have experience with. If it's something terrible like Hibernate, then no wonder. For reference, the ORM I've used the most is Entity Framework (the new one, rewritten for NET Core), and it's…

You just gave me flashbacks to my first job out of college. It was this giant mess of hibernate with a combination of custom SQL queries mixed with the ORM that was responsible for billing data in the billions.

Re: Open-sourcing SQX, a way to build flexible database models in Go

#19

This looks interesting. The only db libraries I can stand are sql query builders. I have experienced way too much pain with orms over the years. They work until you have to do anything slightly complicated and they either get very difficult to use or very slow

It's easy to drop down to pure SQL in every ORM I've ever used. Meanwhile, a good ORM gives you type safe queries, and saves from having to write boilerplate for trivial CRUD. I honestly would like to know which ORMs most critics have experience with. If it's something terrible like Hibernate, then no wonder. For reference, the ORM I've used the most is Entity Framework (the new one, rewritten for NET Core), and it's…

> I honestly would like to know which ORMs most critics have experience with.

I hated Doctrine. I like Django's ORM.

Re: Open-sourcing SQX, a way to build flexible database models in Go

#20

This looks interesting. The only db libraries I can stand are sql query builders. I have experienced way too much pain with orms over the years. They work until you have to do anything slightly complicated and they either get very difficult to use or very slow

It's easy to drop down to pure SQL in every ORM I've ever used. Meanwhile, a good ORM gives you type safe queries, and saves from having to write boilerplate for trivial CRUD. I honestly would like to know which ORMs most critics have experience with. If it's something terrible like Hibernate, then no wonder. For reference, the ORM I've used the most is Entity Framework (the new one, rewritten for NET Core), and it's…

Modern ORMs like Drizzle and Prisma can probably generate more safe and efficient SQL queries than you could write by hand in a fourth of the time and effort
Post reply on HN