Explore tweets tagged as #jsonb
We evaluated GLM-4.6V on BIRD-CRITIC (PostgreSQL SQL generation). Accuracy: 25.3% Works well ✅JSONB manipulation ✅recursive CTEs ✅ON CONFLICT handling Breaks down ❌window functions ❌dynamic schemas ❌query optimization under constraints Execution benchmarks surface
0
0
0
Want to keep JSON data indexed and queryable inside PostgreSQL while maintaining a clean EF Core model? In Stefan’s C# Advent blog, he shows how JSONB + Complex Types in EF Core 10 unlock a true hybrid relational–document approach. https://t.co/auSzCPeKGL
#CSharpAdvent #dotnet
0
0
1
Have any .NET devs heard of or used Jint before? I prototyped some ideas years ago with it. Cool to see it still well maintained and all the ECMAScript features supported now.
18
5
77
What do you think of Hydro? It's powered by MVC, Razor, and AlpineJS.
4
0
5
You can restrict the shape of your jsonb columns so that you don't get unexpected format in your database! Using the pg_jsonschema extension, you can control the shape of your JSONB columns. You might like the freedom with them, but sometimes too much freedom could be unsafe.
5
10
169
Postgres uses TOAST to store large, variable-sized data values like JSONB and TEXT. Using it impacts performance, so you gotta know the tradeoffs. Every row (tuple) is stored in a file that is divided up into 8kb pages. Typically, a single 8kb page can store tens or hundreds of
10
40
310
Crazy idea. Combine MinimalApi.Endpoints with DamianEdwards.RazorSlices and... you've almost reinvented Razor Pages?😅
7
0
53
Avoid using `select *` in your database operations! - Risks of the schema changing in the future, potentially adding a large JSONB column, for example - Might not be able to utilize covering indexes Make sure you always request only what you need from your production database!
28
18
487
Day 01 of PostgreSQL Learning !! > What is PostgreSQL? Architecture > Explored Supabase :) > Databases vs Schema vs Tables > Data Types (SERIAL, UUID, JSONB — supabase loves them) > Primary Keys, Foreign Keys > Constraints: UNIQUE, NOT NULL, CHECK
2
0
10
We chose Postgres over DynamoDB for our new product. Everyone called us crazy. The context: - Building a SaaS analytics platform - Expected complex queries and joins - Team of 4 engineers, all SQL experts - Zero NoSQL experience Why Postgres won: - JSONB handled our flexible
98
65
1K
Insane considering this feature is an experiment and totally vibed. It was too slow so I let GPT-5-Pro tweak it (with @RepoPrompt to give it more context) and now stuff's flying, building virtual rows via jsonb_to_recordset to make the upsert fast.
2
0
17
The new notifications system is coming along nicely; this data will also be the source of generated insights for our customers - Async notification job with Trigger - `activities` table with JSONB metadata - tRPC middleware - system/user generated
14
2
164