How Hillview enforces extra constrains on the relational data model, aka how we discovered Hillview is not quite suitable for this assignment (relational data model) @superliuxz
data does not change while Hillview is running -> the data needs to be immutable. But when we de-duplicate the data from the universal model, we want to take the advantage that we can add a row in the student table easily.
no join support. To fully take advantage of Hillview, we actually need to put everything into a single table -> a universal model (bad)
data does not change while Hillview is running
-> the data needs to be immutable. But when we de-duplicate the data from the universal model, we want to take the advantage that we can add a row in thestudent
table easily.join
support. To fully take advantage of Hillview, we actually need to put everything into a single table -> a universal model (bad)