GORM VS ent

Hello, I want to communicate with a database in my go API. My API is for a website that allows you to track finances and budgets, so the reason I need a database is to store the user's expenses and allow them to search and find each one and which one is costing them the most. I also am going to implement login soon, but I don't think that matters for now. I'm now stuck on how to communicate with my database (Postgres). Should I go with an ORM like gorm, database/sql package, sqlx, or any others? Advice is appreciated

For more information on Gorm's operation of MySQL, please refer to Gorm

To access PlanetScale, we can use ORM from Go called Gorm, and since the PlanetScale database is built on top Vitess (MySQL), install the MySQL driver as well.

Just my opinion, so it it for what it’s worth to you, but I haven’t been especially impressed with the ORM landscape in Go. I have tinkered with a few ORMs - I gave gorm a serious whirl a few months ago, but ended up ditching it in less than a month. If time is on your side, I’d strongly encourage you to experiment with what the standard library’s database/sql package has to offer.

If it is to low-level for your liking maybe take a look at sqlx or even gorm.

Sigh... If you're using gorm V2, you need to pass a dialector to gorm.Open as the first parameter. See the V2 example here: https://github.com/go-gorm/gorm/issues/3565

Framework - Gin ORM - Gorm

I think you are looking for ent https://github.com/ent/ent which has nice graphql integration.

Check out https://entgo.io/ I like the approach to define an entity schema first and let handle entgo the query part.

ent has the nicest integration with graphql (using gqlgen) that I’ve seen with Go, generating almost all the code needed for resolvers and some graphql commons like Node interface and Connection pattern. It also supports PostgreSQL out of the box.

With Atlas, the migration directory can function as the desired state. Thus, you can use Atlas without changing your existing codebase. We use this approach in Ent and it works great for many users. Atlas also supports auth-generating migrations for other migration tools, like Flyway, Liquidbase and various others.

Ent is a framework we created at Facebook and open-sourced a few years ago, and it has grown a lot since then. You're welcome to give the doc a quick read. Still, a summary is it uses a "schema as code" approach based on code generation with plenty of cool features built-in, such as seamless GraphQL/gRPC/OpenAPI integration, hooks, privacy (authorization support), a templating infra that makes it extensible and much more.

Ent is the migration that uses Atlas as a migration engine. The Ariga team maintains both projects.

This is approximately what Ent does.

Try https://github.com/ent/ent :D

I can recommend https://entgo.io/ , ORM with graph semantics + GraphQL/REST/GRPC API generator