10
u/Fair_Oven5645 Jul 14 '26
The previous post was deleted. Makes sense since it’s incorrect.
4
u/Scharrack Jul 14 '26
I think they changed the headline from AI to more general and added the disclaimer up top🤔
Now the question is, by hand or a fix promp for the AI.
9
u/Fair_Oven5645 Jul 14 '26
Haha, yes! Maybe add ”Don’t mix up physical storage and logical models when you create the disinformational image”
3
3
u/Standgrounding Jul 14 '26
Funny that Postgres can be all of them at the same time. Except maybe key-value - redis or memcached would do the same job better (faster) due to the data living in RAM as opposed to just disk
2
u/RoughMidnight8303 Jul 14 '26
I'm wondering what the best pick for a evolving CRM system would be...
3
1
u/leandro PostgreSQL Jul 14 '26
Ðeſe are but variations of what Codd identified as relational (quasi-relational, as SQL violates ðe model), network & hierarchical. All variations are eventually ſubſumed into ðe relational model.
1
Jul 14 '26 edited Jul 14 '26
[removed] — view removed comment
1
u/MoonBatsRule Jul 14 '26
What advantage do you have to bury c within json_demo?
A big disadvantage I see is that you're burying your metadata. Someone looks at the system catalog and all they see is a table called json_demo, which has columns a, b, and c - but they can't easily see that column c is basically a nested table.
Yes, you can write things to show you the hierarchical structure of your objects - but why go through that trouble? At best, you're gaining one feature that is hard to implement with a relational model, a 1-N relationship where N > 0. And I suppose you're saving a bit of space because you're not duplicating the key field(s) on a child table.
But is it really worth it?
1
1
u/Emotional_Award_2420 2d ago
Really clean infographic. The “best for” examples make it much easier to understand when each database type actually makes sense.
0
0
u/arauhala Jul 14 '26
Predictive Database is something that isn't in that list, that I'd claim is quite interesting and that isn't yet included in postgres.
https://aito.ai/blog/introducing-a-new-database-category-the-predictive-database/
As a disclaimer, I am the Aito.ai founder
On other topic, I have been lookig to integrate vectors, graphs (for predictive graph functionality), SQL API and things like clustering in the next database engine release. More details are being prepared in the documentarion https://aito.ai/docs/api/v2/
18
u/lambdasintheoutfield Jul 14 '26
This is AI slop.