3 ms·
It was "optimized" for the aesthetic concerns of RDBMS purists and for ease of implementation of certain other systems, in other words it was optimal for the de
by jeffbee 5y ago
It was "optimized" for the aesthetic concerns of RDBMS purists and for ease of implementation of certain other systems, in other words it was optimal for the developers and severely sub-optimal for the users, which is a problem endemic to RDBMS fandom.
- icedchai 5y agoSo it was basically "write optimized", fully normalized, required at least a half dozen joins to get anything out of it?