1
Remarks, Feed-Backs, Questions
fb:
the audio-quality is a bit poor: pretty "dumb" and low-volumed, so that a respectable
perzeption-le vel is hard to achieve.
But: NOT noisy = good chance for improvement
( = higher "gains" at the mixing-desk & some more trebles)!
r:
1. I felt it courageous, to go for a "column"-wise approach: usually (not on rdbms!)
height-balanced (binary-) node-trees are THE method for "static", no longer
in-use transactional data, - as for it's "unbeatable" quick access, due to minimal
touches/"taken-in-hand" per request to/of the big amounts of data, - in particular,
if these are DRAM-based. But we'll see ...
2. the column-approach reminds me to my n-dim-"cube" for data-validation of the "new" dwh-platform for social-researchers in the huge database of the IAB with all the german
social-insurance-data up from 1974. (SAS-engine, 1999) "Columns" in that respect were
closely refering to 'data-types'.
q: We are apparently talking about non-transactional-data, aren't we?
This topic is an assignment ( ).
HPI Course I, post-lesson 1
Grading will be based on posts submitted to this topic.
This topic will not be visible to users until