id uuid DEFAULT uuid_generate_v4() PRIMARY KEY,
data jsonb,
inserted timestamp with time zone DEFAULT now(),
updated timestamp with time zone
);
1–10 of 15 posts
id uuid DEFAULT uuid_generate_v4() PRIMARY KEY,
data jsonb,
inserted timestamp with time zone DEFAULT now(),
updated timestamp with time zone
);
Use mongoDB without using mongoDB.
uuid version 7 more appropriate for keys in high-load databaseses and distributed systems.
Issues if need something other than uuid_v4. aka v8,
snowflake_id bit more compact than separate uuid_v4 & timezone
json, "blob" storage, not efficent for/optimized for search/replace operations. Json blob will need to be normalized every time data cached. File system storage with uuid_v7 index less overhead.
Care to example some usage cases? And why uuid over auto-increment sequenced number?
Sometimes it’s fine and the simplicity is worth it if you aren’t dealing with a distributed database, but a random uuid is a better default in my opinion.
Depends. Having a real schema can help with performance and correctness guarantees.
Tell me you have never built a real world production application without telling me you have never built a real world production application.
200k users a month, not huge but not nothing
Why do you think it's a bad schema?