reaanb2

4 ms·

1.
by reaanb2 28d ago
This article describes the OOP approach that leads to object-relational mapping, boilerplate code, database schema duplicated in code, navigational data access and the impedance mismatch. It defines OOP around data modeling and taxonomy, ra
2.
by reaanb2 1mo ago
It's not a new or exotic conceptualization, it's a recovery of the semantics that Codd had in mind and well defined in fact-oriented modeling approaches like object-role modeling / NIAM and FCO-IM. It provides conceptual pars
3.
by reaanb2 2mo ago
Can we also move on from speaking about rows as if they're vertices in the conceptual model graph, and start treating them as n-ary associations / facts?
4.
by reaanb2 2mo ago
FCO-IM elegantly bridges the gap between data and language. Has anyone tried/compared SQL query generation based on that?
5.
by reaanb2 3mo ago
We had general-purpose graph databases before graph databases became a thing. I'm talking about relational databases. Values are the vertices, tuples are the edges, FK constraints are inclusion dependencies. In fact, n-ary relations me
6.
by reaanb2 1y ago
Trying to placate the gods who are busy destroying their world...
7.
by reaanb2 1y ago
A better solution would be to move away from object-oriented domain modeling towards SQL-speaking entity-component systems.
8.
by reaanb2 1y ago
That's a cool approach that could work well if you don't need realtime data validation such as in a UI. I would love to find a solution that allows the same validation rules to be used in the DBMS as well as in the backend and fro
9.
by reaanb2 1y ago
I disagree. From a fact-oriented modeling perspective, relationships among entities are already well-modelled and represented in tables. There's a reason the relational model calls tables relations - they relate things. The mistake her
10.
by reaanb2 1y ago
In my view, the O/R impedance mismatch derives from a number of shortcomings. Many developers view entities as containers of their attributes and involved only in binary relationships, rather than the subjects of n-ary facts. They map
11.
by reaanb2 1y ago
See https://arxiv.org/abs/2312.00638 for one proposal to address this
12.
by reaanb2 1y ago
In real life, insurance often doesn't pay for everything and service providers would need to support capturing both sets of info, not either one or the other. But that's beside the point. Properly naming check constraints can go a
13.
by reaanb2 1y ago
EF is limited to binary relationships: https://learn.microsoft.com/en-us/ef/core/modeling/relations... . When entities are mapped to rows and relationships to foreign key constraints, it results in a netw
14.
by reaanb2 1y ago
"Object-relational mapper" is a misnomer, they should be called network data model to SQL mappers. They're not primarily for mapping between different arrangements of the same data, but about recreating a network data model p
15.
by reaanb2 1y ago
If you don't pay for the product, you are the product.
16.
by reaanb2 2y ago
> you need software to map the relations to objects If you start with a network data model perspective and build that into your system, then it follows that you'll want a network data model to SQL mapper. That's what ORMs are,
17.
by reaanb2 2y ago
Consciousness for me is tied to internal modeling of the world and oneself in it. An agent without an internal model is limited to reacting to immediate inputs, and constrained in terms of the complexity of memory it can have. It could sens
18.
by reaanb2 2y ago
How does this compare to a relational database, where hyperedges are represented by tables and vertices by values?
19.
by reaanb2 2y ago
Systemantics by John Gall provides valuable perspectives into system effectivesness, efficiency and robustness.
20.
by reaanb2 2y ago
A more appropriate name for ORMs would be "network data model to SQL mappers". They don't facilitate good OOP and oppose relational thinking and data management.
21.
by reaanb2 2y ago
An OOP domain model in an information system is like trying to build a car using a roadmap instead of an engineering diagram. The value of OOP becomes clearer when used to decompose and construct the solution rather than the problem space.
22.
by reaanb2 6y ago
I've been looking for task tracking / planning software with some project management features, like the ability to decompose tasks into subtasks, estimate duration and priority and specify dependencies among tasks. However, the so