ent VS SQLBoiler

Hey! If you're interested in databases and APIs (e.g. GraphQL and OpenAPI), you are welcome to Ent (github.com/ent/ent). We have a really friendly community, and you can feel free to ping me on our Slack channel or Discord server if you need guidance. Good luck!

Use https://entgo.io/ it will allow you to manage a complex schema without worrying about the actual storage

Yes of course https://entgo.io/

Check out this new blog post we wrote about a new flow for reporting and triaging bugs that we created for Ent using template repository and Codespaces.

Hi, I think you should have a look at https://entgo.io/ , it will give you all the benefits of a graph database using technology like MySQL for example. It's used in many places and the community is very helpful.

If you never heard about Ent before, see our GitHub repository: https://github.com/ent/ent, or our website: https://entgo.io.

re ent + tx outbox, a discussion started on this issue https://github.com/ent/ent/issues/1473. i think its a great idea and with all of the "NewSQL" databases that support proper horizontal scaling, i think it will become a very widely used design pattern.

- Ent consistency checkers/fixers (I forget the name of the framework/tool)

It's sad to think that people's only glimpse into these tools is through https://entgo.io which is a really crude approximation of the real thing due to Go's lack of generics and expressiveness. Imagine if such amazing tools could be used at actually ethical companies.

[1] https://www.micahlerner.com/2021/10/23/ramp-tao-layering-ato...

If you use https://entgo.io/ you get it as a built in feature for all your models. https://entgo.io/docs/tutorial-todo-gql-paginate

https://github.com/volatiletech/sqlboiler cause is nice to have type safety, or sqlc, I use sqlx most of the time

Other people maintain https://github.com/volatiletech/sqlboiler which is pretty good, though I wish it were a bit more flexible, but it may be a little faster to get started with.

I have been using sqlboiler. In my honest opinion it is the best ORM. You can see benchmark here https://github.com/volatiletech/sqlboiler

It seems you forgot sqlboiler [1] which is something like "write SQL schema, parse SQL schema, generate Go structs and functions to query the schema". Not quite like generating activerecords, I think.

[1]: https://github.com/volatiletech/sqlboiler

I was expecting the article to contain a note about SQLBoiler (https://github.com/volatiletech/sqlboiler) and why they didn't use it, but there is no. So I was expecting SQLBoiler to be heavily mentioned in the comments, but it's not the case.

I you want to see a (slightly heated) debate about `sqlc` versus SQLBoiler with their respective creators: https://www.reddit.com/r/golang/comments/e9bvrt/sqlc_compile...

Note that SQLBoiler does not seem to be compatible with `pgx`.

You might want to have a look into SQLBoiler. https://github.com/volatiletech/sqlboiler

Consider SQL Boiler because it can integrate directly with an existing database.

Depending on your preferences, sqlboiler uses the DB as source of truth for generating structs and has nice querying features

DB Management: https://github.com/volatiletech/sqlboiler -- this follows a data first model, aka your database schema will create go code, not the django way where Py code updates the DB. https://github.com/amacneil/dbmate -- I use it to manage my DB schema.