bqb
BQB is a lightweight and easy to use query builder that works with sqlite, mysql, mariadb, postgres, and others. (by nullism)
errors
Simple error handling primitives (by pkg)
| bqb | errors | |
|---|---|---|
| 13 | 30 | |
| 125 | 7,511 | |
| - | - | |
| 6.0 | 0.2 | |
| 7 days ago | over 2 years ago | |
| Go | Go | |
| MIT License | BSD 2-clause "Simplified" License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
bqb
Posts with mentions or reviews of bqb.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-03-11.
-
Are there any decent ORMs in Golang?
But using a query builder, something like squirrel or (plug) bqb, allows you to actually write SQL (or something close to it) when you need it but also handles the nasty string building bits. Though I agree that ORMs are not always bad, especially for small projects with well-defined scope.
- Examples of Good Go Repos
-
GORM
Plug for bqb as a query builder, but there's also squirrel which works pretty well too.
-
Best packages?
(plug) bqb for very simple query building.
-
ORM vs SQL Builder in Go
Squirrel is great! Let me also plug bqb.
-
Open Source Go Projects for learning go
Plug: BQB (basic query builder) is small, 100% test coverage, and in AwesomeGo. A great starter project.
-
Where to find a virtual or local Go mentor?
I totally understand this. If you do go with a query builder, may I recommend bqb (shameless plug) as it allows you to remain closer to the SQL than some alternatives and doesn't do anything fancy. We stripped out 50% of our query logic with it in our org, which has enabled us to more readily tweak the SQL for performance.
-
Does gorm worth learning?
There's also bqb. We use it in production at our company -- much better than raw SQL. If you couple it with something like scany then you get more of the ORM benefits without the complexity.
-
Any "simple" projects with particularly well-written and/or well-documented code for a beginner to look through?
Another shameless plug: https://github.com/nullism/bqb pretty tiny query builder with 100% test coverage
-
bqb VS Squirrel - a user suggested alternative
2 projects | 9 Sep 2021
errors
Posts with mentions or reviews of errors.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-11-29.
-
Show HN: Error return traces for Go, inspired by Zig
Can you explain why we should this over https://github.com/pkg/errors?
-
Cant wait for less verbose error handling
The pkg/errors package offers some nice add-ons for easier error handling. Too bad it was put into maintenance mode pending whatever changes/improvements are coming in Go 2.
- Error handling and serializing
-
isse for go path in neovim
I can't figure out the issue so here for some help, I am using `neovim/nvim-lspconfig` my `gopls` doesn't recognise external paths such as `github.com/pkg/errors` , it throws error`could not import github.com/pkg/errors (cannot find package "github.com/pkg/errors" in any of /usr/local/go/src/github.com/pkg/errors (from $GOROOT) /Users/ra compiler (BrokenImport)\`
-
What am I supposed to be doing with errors?
Also - there are some error handling utils that allow you to wrap errors before passing: https://github.com/pkg/errors
-
Go error handling is not verbose but the error handling itself.
Should've been something like errors.Newf("failed to foofoo %s", foo) instead and preferably never invent %w but have some controlled way to wrap like errors.Wrapf(err, "failed to foofoo %s", foo) that was in ye olde github.com/pkg/errors.
-
How to wrap the error best?
Prefer using errors.Wrap and errors.Wrapf from https://github.com/pkg/errors . It's frozen because they don't want to add features, waiting for a re-write of error handling in Go2.
- mdobak/go-xerrors: Yet another error handling library.
-
Getting at the type of error after it has been wrapped with errors.Wrap
Im using zerolog and in order to get the stack trace for my error I have to wrap my error in errors.Wrap from "github.com/pkg/errors".
-
When ia a good time to panic?
And for "real programs" you can use https://github.com/pkg/errors (if you want stack traces)
What are some alternatives?
When comparing bqb and errors you can also consider the following projects:
Squirrel - Fluent SQL generation for golang
zerolog - Zero Allocation JSON Logger
goqu - SQL builder and query library for golang
autoflags - Populate go command line app flags from config struct
pgweb - Cross-platform client for PostgreSQL databases
go-multierror - A Go (golang) package for representing a list of errors as a single error.
Tile38 - Real-time Geospatial and Geofencing
logrus - Structured, pluggable logging for Go.
cockroach - CockroachDB - the open source, cloud-native distributed SQL database.
bitio - Optimized bit-level Reader and Writer for Go.
badger - Fast key-value DB in Go.
Testify - A toolkit with common assertions and mocks that plays nicely with the standard library