sqlite | SQLBoiler | |
---|---|---|
73 | 42 | |
- | 6,477 | |
- | 1.6% | |
- | 7.7 | |
- | 12 days ago | |
Go | ||
- | BSD 3-clause "New" or "Revised" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
sqlite
- Show HN: Roast my SQLite encryption at-rest
-
Show HN: My Go SQLite driver did poorly on a benchmark, so I fixed it
> I would've probably picked the modernc variation
Heads up about the modernc library, it has been stuck on an old version of sqlite for several months [1]. It seems like maintainer time is the limiting factor [2]. There has been a call to arms on that issue page, the maintainer is looking for help, but it looks like not much has arrived. It seems like it might trace back to blockers in the C-to-Go compiler.
It's a major undertaking and a very impressive piece of work, but I'm not surprised it's a struggle when big roadblocks get hit. I hope they find a way to progress, but I'm very relieved to be seeing some CGo-free alternatives like ncruces/go-sqlite3 emerging. I'm going to give it a try for sure and see if I can live with the compromises.
Squinn-go looks very compelling too, but I don't like that it requires the squinn binary to already be installed on a user's machine, I think that gives with one hand and takes with the other: sure, I get to avoid CGo, but I also lose the turnkey, single-command install, static build benefits Go brings out of the box.
Seconding the point about nitty gritty, I'd read it for sure too!
[1]: https://gitlab.com/cznic/sqlite/-/issues/154
-
Show HN: Sqinn-Go is a Golang library for accessing SQLite databases in pure Go
No, but that has the disadvantage of being C compiled into Go, then being compiled into native executable.
I'm actually surprised by how readable this came out; props to the Go->C compiler author. But you can guess that pushing this sort of thing through the Go compiler is going to cause some slowdowns due to sheer paradigm mismatch: https://gitlab.com/cznic/sqlite/-/blob/master/lib/sqlite_lin...
-
Show HN: MongoDB Protocol for SQLite
FWIW, we use a version of SQLite transpiled into Go to avoid CGI problems: https://gitlab.com/cznic/sqlite
-
Go port of SQLite without CGo
It could be clearer in the readme, but note that this is a machine translation from C to Go, repeated for every OS-Arch pair. Example of the one you're most likely to use in production: https://gitlab.com/cznic/sqlite/-/blob/master/lib/sqlite_linux_amd64.go
SQLBoiler
-
Go ORMs Compared
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.
-
Comparing database/sql, GORM, sqlx, and sqlc
Moved all my projects to https://github.com/volatiletech/sqlboiler.
-
Are there any decent ORMs in Golang?
sqlboiler
-
Any mid sized / big open source code base in golang that makes use of SQL DBs?
My current ORM of choice is Bob [GitHub Link] which I created based on my experience using and maintaining SQLBoiler [GitHub Link].
-
GORM
You mean like ORMs? * sqlboiler: generates Go ORM using database schema.
-
ORM or no ORM (and which ones)?
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.
-
Using Prisma Migrate with a Dockerized Postgres
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.
-
Can anyone help me on how you are using golang with databases in production systems?
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.
- volatiletech/sqlboiler: Generate a Go ORM tailored to your database schema.
-
Go overtook Ruby and ranked #3 among the most used backend languages for pull requests since 2021
FWIW, the other posts point to https://gobuffalo.io/ and https://github.com/volatiletech/sqlboiler as possibilities.
What are some alternatives?
chai - Modern embedded SQL database
GORM - The fantastic ORM library for Golang, aims to be developer friendly
ffi-overhead - comparing the c ffi (foreign function interface) overhead on various programming languages
sqlc - Generate type-safe code from SQL
sqlite - Go SQLite3 driver
ent - An entity framework for Go
go-sqlite3 - sqlite3 driver for go using database/sql
sqlx - general purpose extensions to golang's database/sql
sqlparser-rs - Extensible SQL Lexer and Parser for Rust
go-pg - Golang ORM with focus on PostgreSQL features and performance
proteus - A simple tool for generating an application's data access layer.
upper.io/db - Data access layer for PostgreSQL, CockroachDB, MySQL, SQLite and MongoDB with ORM-like features.