pgxmock
usql
| pgxmock | usql | |
|---|---|---|
| 2 | 21 | |
| 282 | 8,619 | |
| - | 0.7% | |
| 8.1 | 9.2 | |
| 9 days ago | 5 days ago | |
| Go | Go | |
| GNU General Public License v3.0 or later | MIT 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.
pgxmock
-
Using SQLC in project how do I mock database Calls with it for unit testing?
It's not the right call IMO to skip mocking the database connection to achieve 100% test coverage. How your app will behave in failure scenarios that are impossible to imitate during integration tests is part of the software contract. If your choice is to panic, or return an error, document that by testing that behavior. If another dev, or future you inadvertently breaks the contract, the test suite will fail. That's what you want. For unit tests against your database you should be using either go-sqlmock if testing against database/sql or pgxmock if testing against pgx. That being said, the points raised elsewhere in this thread regarding unit tests potentially hiding edge cases in terms of how an actual database will interact with your application that are not reflective of your understanding when writing mocks are 100% valid. You should do both. Unit test your app and write integration tests as well. On my team, we run integration tests using docker-compose.
-
Can you set expectations for SQL transaction using Testify?
For postgres only but pgxmock is similarly excellent
usql
- xo/usql: Universal command-line interface for SQL databases
- Usql – Universal command-line interface for SQL databases
-
PRQL a simple, powerful, pipelined SQL replacement
Also all languages has an query-builder / ORM so the benefit of something like PRQL is possibly not big enough to merit it as an additional dependency.
My suggestion:
Make PRQL a cli tool that can be used by allowing users to connect to a database in a similar fashion as something like usql (https://github.com/xo/usql),
-
Is there a CLI interface to browse SQL databases?
take a look at: https://github.com/xo/usql
-
New Open source Go projects looking for contributors
https://github.com/xo/usql has some good first issues
-
usql 0.11.0
There's a new release of usql that adds even more autocomplete and fixes a bunch of issues: https://github.com/xo/usql/releases/tag/v0.11.0
- 5 Useful Database Command Line Tools
- usql
-
Literate programming is much more than just commenting code
I am not a big fan of the complex literate programming style involving code-generation which this article talks about.
But I recently discovered that Google's zx [1] scripting utility supports executing scripts in markdown documents and I combined it with httpie [2] and usql [3] for a bit of quick and dirty automation testing and api verification code and it worked out pretty well.
[1] https://github.com/google/zx#markdown-scripts
[2] https://github.com/httpie/httpie
[3] https://github.com/xo/usql
- usql v0.9.4
What are some alternatives?
go-sqlmock - Sql mock driver for golang to test database interactions
go-sitemap-generator - go-sitemap-generator is the easiest way to generate Sitemaps in Go
pgxatomic - Clean implementation of transaction manager using pgx
hystrix-go - Netflix's Hystrix latency and fault tolerance library, for Go
goose - A database migration tool. Supports SQL migrations and Go functions.
boilr - :zap: boilerplate template manager that generates files or directories from template repositories
Task - A task runner / simpler Make alternative written in Go
ngrok - Unified ingress for developers
fzf - :cherry_blossom: A command-line fuzzy finder
hub - A command-line tool that makes git easier to use with GitHub.
peco - Simplistic interactive filtering tool
grequests - A Go "clone" of the great and famous Requests library