pg_jsonschema
pg_ivm
pg_jsonschema | pg_ivm | |
---|---|---|
15 | 19 | |
929 | 774 | |
1.6% | 2.2% | |
6.6 | 6.3 | |
20 days ago | about 1 month ago | |
Rust | C | |
Apache License 2.0 | GNU General Public License v3.0 or later |
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.
pg_jsonschema
-
Introducing pgzx: create PostgreSQL extensions using Zig
And lots of interesting extensions use it, like
https://github.com/tembo-io/pgmq
https://github.com/zombodb/zombodb
https://github.com/supabase/pg_jsonschema
-
Beyond SQL: A relational database for modern applications
> In other words, there is still a (lossy) translation layer, it just happens to be in the RDBMS rather than in-app.
It's not lossy if your application can guarantee a json <-> datatype roundtrip and the json is validated with jsonschema (generated by your application)
In Rust it's something like this
https://serde.rs/ to do the data type <-> json mapping
https://docs.rs/schemars/latest/schemars/ to generate jsonschema from your types
https://github.com/supabase/pg_jsonschema to validate jsonschema in your database (postgres). with this setup it's interesting (but not required) to also use https://docs.rs/jsonschema/latest/jsonschema/ to validate the schema in your application
-
FerretDB, a truly open-source MongoDB alternative
Pretty exciting!
What about optionally validating some columns with jsonschema? Perhaps using https://github.com/supabase/pg_jsonschema - is using other postgres extensions supported in FerretDB? (if not, maybe it's feasible to incorporate the code of pg_jsonschema in FerretDB?)
- Type Constraints in 65 lines of SQL
-
Ask HN: Do you use JSON Schema? Help us shape its future stability guarantees
I'm not currently using it, but I'm strongly considering validating json in postgres with https://github.com/supabase/pg_jsonschema - which uses the https://docs.rs/jsonschema/latest/jsonschema/ Rust crate
So I'm not sure if my feedback is valid but, I sure hope that the jsonschema crate follows the spec! Otherwise I'll never use jsonschema but instead something-not-exactly-jsonschema. In other words.. you better not break anything.
-
Features I'd Like in PostgreSQL
Sounds dumb, but I want JSON field schema validation. I added a JSON column for flexible data, and although I'm happy with its flexibility, I kinda hope I can validate the JSON data structure. Recently I just found an extension [1] and will try soon.
[1] https://github.com/supabase/pg_jsonschema
-
Dynamic JSON schema validation, how can I do that in Postgres?
https://github.com/supabase/pg_jsonschema is new and looks good
-
Supabase Beta July 2022
Born as an excuse to play with pgx, pg_jsonschema is a solution we're exploring to allow enforcing more structure on json and jsonb typed postgres columns. Only 10 lines of code 😎
- GitHub - supabase/pg_jsonschema: PostgreSQL extension providing JSON Schema validation
- Show HN: Pg_jsonschema – A Postgres extension for JSON validation
pg_ivm
- Postgres is eating the database world
-
What Is Incremental View Maintenance (IVM)?
FTA, because I don't like Jeopardy questions in headlines:
“Incremental View Maintenance (IVM) provides a method for keeping materialized views current by calculating and applying only the incremental changes, as opposed to the complete recomputation of contents performed by the REFRESH MATERIALIZED VIEW command.”
Article shows using the pg_ivm Postgres extension available here: https://github.com/sraoss/pg_ivm
- Pg_ivm: Incremental View Maintenance as a Postgres Extension
- Anyone have experience with incremental materialized views in postgres?
- Incremental View Maintenance for PostgreSQL
-
a temporary-ish table vs materialize view?
There is an extension that provides some limited incremental MVIEW refresh: https://github.com/sraoss/pg_ivm
- Features I'd Like in PostgreSQL
- IVM (Incremental View Maintenance) Implementation as a PostgreSQL Extension
-
Materialized View: SQL Queries on Steroids
There’s awesome work being done on incremental view maintenance in postgres:
https://github.com/sraoss/pg_ivm
-
Should I replace all db select query REST APIs with a single generic router ?
It makes sense to perform managed denormalization - use a materialized view or automatically refresh a table or foreign server (via FDW) using common triggers (like pg_ivm does). And it's fine to add a TTL to it and use as a read store... update on user login and make a partial index just for that. And that's how you could get CQRS...
What are some alternatives?
windmill - Open-source developer platform to turn scripts into workflows and UIs. Fastest workflow engine (5x vs Airflow). Open-source alternative to Airplane and Retool.
prawn-stack - A pageview counter using the AWS free tier, Postgres, Node and React
postgres-json-schema - JSON Schema validation for PostgreSQL
materialize - The data warehouse for operational workloads.
pgx - Build Postgres Extensions with Rust! [Moved to: https://github.com/tcdi/pgrx]
pg_hint_plan - Extension adding support for optimizer hints in PostgreSQL
is_jsonb_valid - Native PostgreSQL extension to validate jsonb
contour - Contour is a Kubernetes ingress controller using Envoy proxy.
auth - A JWT based API for managing users and issuing JWT tokens
OpenLogReplicator - Open Source Oracle database CDC
jsonschema - JSON Schema validation library
risingwave - Cloud-native SQL stream processing, analytics, and management. KsqlDB and Apache Flink alternative. 🚀 10x more productive. 🚀 10x more cost-efficient.