3 ms·
If this is representative of your database: CREATE TABLE tasks ( id BIGINT GENERATED ALWAYS AS IDENTITY, created_at TIMESTAMPTZ DEFAULT CURRE
by SoftTalker 2y ago
If this is representative of your database:
CREATE TABLE tasks (
id BIGINT GENERATED ALWAYS AS IDENTITY,
created_at TIMESTAMPTZ DEFAULT CURRENT_TIMESTAMP,
args JSONB,
PRIMARY KEY (id)
);
Then Postgres (or any relational DB) is the wrong choice.
Is this how developers view a database in 2025? A place to store a JSON blob?
- ceejayoz 2y agoPostgres is a perfectly acceptable key/value store if you need it for that.
- williamdclt 2y agoIts trade offs. If you already have Postgres in place for other use-cases, using it for this purpose is a completely valid trade-off. If transactionality is important, it’s a valid trade off. If I don’t need what other data store would give me (perf, HA writes), why would I bother setting up and operating a completely separate system. And even for non relational use cases, Postgres is still a better option in many cases
- VWWHFSfQ 2y agoThis is perfectly reasonable if you need document features in some tables. I would strongly prefer this over something like Mongo DB.
- tucnak 2y agoYour example demonstrates how little of PostgreSQL syntax you actually know.
- SoftTalker 2y agoIt's not my example. Copied from TFA.
- wewewedxfgdf 2y agoPostgres has very sophisticated JSON querying and storage.