groundup VS SQLBoiler

I did that from https://github.com/golangast/groundup

I don't think this project is mainstream and I can see others argue not beginner friendly.... But if you are bored I do need help in https://github.com/golangast/groundup

This is more of an idea generator than a project and it has a lot of issues but really I just want an app where you generate parts of a website for your own thing. https://github.com/golangast/groundup

I am building this which is basically a learning project and very beta if you can even call it that. More like an idea incubator then an app. https://github.com/golangast/groundup

I'm building a code generator in go and it's a lot of fun. It gets sometimes hard but not in a crazy way. You can use whatever you want from it. https://github.com/golangast/groundup

If you want more control then I am in the middle of making something that generates code but it's not blog ready. You might be able to look at the code and take it. I'm just doing it to learn. https://github.com/golangast/groundup

Project - https://github.com/golangast/groundup

SQLBoiler takes a database-first approach, generating Go code from your database schema. This means it creates highly optimized and custom-tailored code for your specific database schema. SQLBoiler is great for applications where the database schema is well-defined and changes infrequently. However, like sqlc, it requires regenerating the code when the database schema changes. It's well-suited for projects where performance is a key concern and the database design is stable​.

Moved all my projects to https://github.com/volatiletech/sqlboiler.

sqlboiler

My current ORM of choice is Bob [GitHub Link] which I created based on my experience using and maintaining SQLBoiler [GitHub Link].

You mean like ORMs? * sqlboiler: generates Go ORM using database schema.

SQL code generator (aka inspect a database or SQL files to generate data models). You have the option of using something like volatiletech/sqlboiler which looks at the a physical database and generates code based on the schema. Or SQLC which is an amazing and fast project.

After trying a half dozen migration engines for NodeJS, I was pleased to see Prisma and its excellent documentation. As a golang developer I am partial to SQLBoiler and its database-first approach, though perhaps this is a condition of our community where we want all the knobs. Prisma was code-first but still gave me enough control to feel confident.

I use sqlboiler which generates an ORM from your database, and sql-migrate which is a tool for managing SQL migrations. Although you have to write your migrations in SQL, which IMHO is a plus.

FWIW, the other posts point to https://gobuffalo.io/ and https://github.com/volatiletech/sqlboiler as possibilities.