pg-typesafe
Shares rank 7 of 8 SQL query builders by recommenders
Recommended for typed PostgreSQL queries in TypeScript that catch misspelled column names, an improvement on pgtyped. Critics say dynamic queries and composability are hard.
Recommended for typed PostgreSQL queries in TypeScript that catch misspelled column names, an improvement on pgtyped. Critics say dynamic queries and composability are hard.
6 people gave an opinion
- recommend it
- 5
- criticize it
- 1
- approval share
- 83%
Recommended in 1 of 13 months
- November 2025: not recommended
- December 2025: not recommended
- January 2026: not recommended
- February 2026: recommended
- March 2026: not recommended
- April 2026: not recommended
- May 2026: not recommended
- June 2026: not recommended
- July 2026: not recommended
- August 2026: not recommended
- September 2026: not recommended
- October 2026: not recommended
- November 2026: not recommended (month in progress)
Why it doesn’t carry the badge
- 5 people recommend itNeeds 10 or more, not met.
- 5 recommenders for every criticNeeds 2 to 1 or better, met.
- Recommended in 1 of 13 monthsNeeds 4 or more, not met.
The same three rules apply to every product, and the badge can’t be bought. How the badge works
What people say about it
The reasons people give, with the number of comments that give each one. Open a reason to read what they said.
Why people recommend it
Each mark is one comment
Seen as cool, worth trying
“Seems very cool, if it works”
Comment from 18 Feb 2026 in “Show HN: Pg-typesafe – Strongly typed queries for PostgreSQL and TypeScript” “Very cool! I'll try it out!”
Comment from 18 Feb 2026 in “Show HN: Pg-typesafe – Strongly typed queries for PostgreSQL and TypeScript”
What people warn about
Each mark is one comment
Hard to handle dynamic queries
“I haven’t found a good way to handle dynamic queries in pg-typesafe yet.”
Comment from 18 Feb 2026 in “Show HN: Pg-typesafe – Strongly typed queries for PostgreSQL and TypeScript”
Other SQL query builders people recommend
The four most recommended other SQL query builders, with the same counts for each, so you can compare like for like. The tick on each bar marks the 2 to 1 line the badge needs.
| Product | Recommend | Criticize | Approval | Months | Owned | Badge |
|---|---|---|---|---|---|---|
| sqlc | 20 | 4 | 83% | 9 | — | Approved |
| Ecto (Elixir) | 17 | 5 | 77% | 8 | — | Approved |
| sqlx | 13 | 4 | 76% | 8 | — | Approved |
| jOOQ | 13 | 3 | 81% | 6 | — | Approved |
| pg-typesafeThis page | 5 | 1 | 83% | 1 | — | — |
What people said
7 of the 8 comments that mention it, newest first. Each links to the original comment.
“Very cool! I'll try it out!”
“The lack of composability makes this a hard no for me”
“you won’t cause problems when spelling the column names”
“I haven’t found a good way to handle dynamic queries in pg-typesafe yet.”
“This looks like a nice improvement on pgtyped, and another good option.”
“Seems very cool, if it works”
“writing SQL directly is more convenient”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.