You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Session keys now use SHA-256 hash instead of raw token strings
20
20
* Removed hardcoded JWT secret from sample config
21
+
* RPC calls now emit named parameters in a deterministic order (function-signature order, falling back to alphabetical), so `pg_stat_statements` aggregates identical calls under a single `queryid` instead of one per JSON key permutation
22
+
* M2M view relationship synthesis now deterministically prefers view junctions over base-table junctions (fixes a flaky "permission denied" error when the base junction lived in a schema the caller lacked USAGE on)
Copy file name to clipboardExpand all lines: README.md
+5-1Lines changed: 5 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ It is mostly compatible with [PostgREST](https://postgrest.org/en/stable/), with
8
8
9
9
The main differences are:
10
10
11
-
* SmoothDB is in development and beta quality. Prefer PostgREST for now, which is rock solid
11
+
* SmoothDB is actively developed and maturing quickly; PostgREST remains the more battle-tested option for critical production workloads
12
12
* SmoothDB is faster and has a lower CPU load
13
13
* It is written in Go
14
14
* Can be used both stand-alone and as a library (the main motivation for writing this)
@@ -19,6 +19,10 @@ The main differences are:
19
19
See [TODO.md](TODO.md) for the many things to be completed.
20
20
Please create issues to let me know your priorities.
21
21
22
+
## About this project
23
+
24
+
SmoothDB is not *vibe-coded*. It was started in 2022 as a solid, versatile middleware meant to serve as a reliable building block for data-driven applications. Since 2025 we have been pairing that foundation with strong LLMs to harden, review, and extend the code — aiming to follow the high bar set by PostgREST in correctness, safety, and API fidelity.
0 commit comments