dbt-unit-testing
graphjin
dbt-unit-testing | graphjin | |
---|---|---|
7 | 61 | |
404 | 2,839 | |
1.5% | - | |
7.7 | 5.5 | |
16 days ago | 2 days ago | |
Shell | Go | |
MIT License | Apache License 2.0 |
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.
dbt-unit-testing
-
The SQL Unit Testing Landscape: 2023
If you use dbt for transformations Dbt Unit Testing (https://github.com/EqualExperts/dbt-unit-testing) is getting some attention (https://www.thoughtworks.com/radar/languages-and-frameworks?blipid=202304042)
-
Data-eng related highlights from the latest Thoughtworks Tech Radar
dbt-unit-testing
- I'm not getting it...what's the point of DBT?
-
Ask HN: How do you test SQL?
We use this and take an example-based tests approach for any non-trivial tables: https://github.com/EqualExperts/dbt-unit-testing
-
SQL should be your default choice for data engineering pipelines
> How do you test some SQL logic in isolation?
I do this using sql
1. Extracting an 'ephemeral model' to different model file
2. Mock out this model in upstream model in unit tests https://github.com/EqualExperts/dbt-unit-testing
3. Write unit tests for this model.
This is not different than regular software development in a language like java.
I would argue its even better better because unit tests are always in tabular format and pretty easy to understand. Java unit tests on other hand are never read by devs in practice.
-
Unit testing with dbt
I haven't done it yet but there are some popular blogs as well as a DBT package someone created.
-
Modern Data Modeling: Start with the End?
> I really don’t understand the communities obsession with unwieldy tools like DBT.
It lets me write test first sql transforms. I never thought TDD sql would be possible. My sql is so much more readable with common logic extracted into ephmeral models. I practice same method to write clear code to write sql, eg: too many mocks = refactor into separate model ( class) .
I think DBT made this possible with refs that can be swapped out with mocks. This is the awesome library I am using https://github.com/EqualExperts/dbt-unit-testing
graphjin
- [Golang] Super Graph GraphQL au compilateur SQL renommé GraphJin et prend maintenant en charge MySQL
-
Does Go, has something similar to Laravel eloquent (ORM) ?
This one looks interesting if you like GraphQL… https://graphjin.com
-
Looking for library recommendations: Django -> Golang port
You're right. Django made a ton of tables, and it's pretty insightful to think about all the stuff it's trying to consider and a nightmare to migrate that framework. Django might have simplified some stuff, but it's still too opaque for my taste and the overall end goals of the project. Currently, I'm testing using graphjin (it doesn't have the best documentation, but it does boast an SQL generation capability that I philosophically think is the best way to do things).
-
Advice on ORMs with REST/GraphQL & Hasura/PostGraphile implementation
Checkout GraphJin it's an automatic GraphQL to SQL compiler, you write your database queries in GraphQL instead of SQL and it compiles them into efficient SQL on the fly. Works as a library in GO and NodeJS. https://github.com/dosco/graphjin
-
Ask HN: How do you test SQL?
In GraphJin an automatic GraphQL to SQL compiler we use the gnomock library it startups a database instance (docker) then create the schema and tests data and finally our code connects to it and runs a series of tests. We run these across Mysql, Postgres and a few other DB's. Gnomock supports a wide range of them. Right now we don't take down the db for every test only between test runs but its fast enough that we could. This whole thing runs of a simple `go test -v .` command and we run it on every commit using a githook. https://github.com/dosco/graphjin/blob/master/tests/dbint_te...
- Should I use GraphQL for a public facing API (in place of a REST API)?
- GraphJin 2.0 - A new kind of ORM for GO
-
Multiple subscriptions fom apollo aclient.
This was a bug in GraphJin it has since been fixed. The issue was that you were trying to have multiple subscriptions over a single websocket this did not work (it should) and now it does. https://github.com/dosco/graphjin/commit/43e619b2ff392dd42b99a4d56074a041a54b0e1c
-
Is graphql-request a good tool for only client side api? Share your feedbacks. Thanks 🙏
Not exactly GraphQL is just a format to define what data you want back from someplace. You can use it in a browser app to request data from a backend GraphQL server or you can use it as an ORM within your backend app to fetch data from a database using a library like GraphJin. https://github.com/dosco/graphjin
- Graphjin.js - An easy-to-use, zero dependency Node.js library to build APIs quickly
What are some alternatives?
sqlglot - Python SQL Parser and Transpiler
Hasura - Blazing fast, instant realtime GraphQL APIs on your DB with fine grained access control, also trigger webhooks on database events.
data-diff - Compare tables within or across databases
graphql-go - GraphQL server with a focus on ease of use
dbt-expectations - Port(ish) of Great Expectations to dbt test macros
gqlgen - go generate based graphql server library
sqlx - 🧰 The Rust SQL Toolkit. An async, pure Rust SQL crate featuring compile-time checked queries without a DSL. Supports PostgreSQL, MySQL, and SQLite.
asciinema - Platform for hosting and sharing terminal session recordings
SS-Unit - A 100% T-SQL based unit testing framework for SQL Server
graphql-benchmarks - GraphQL benchmarks using the-benchmarker framework.
hash-db - Experimental distributed pseudomultimodel keyvalue database (it uses python dictionaries) imitating dynamodb querying with join only SQL support, distributed joins and simple Cypher graph support and document storage
node-pg-migrate - Node.js database migration management for PostgreSQL