introduce indexes #34
Description
Currently we have no indexes except for the primary keys defined. We need to decide what should be indexed and how to handle indexing for the user created data tables. Should we give index creation power to the user? Should we index everything?
Activity
detman commentedon Feb 25, 2016
index power just means more performance when doing queries? or more functionality?
splitbrain commentedon Feb 25, 2016
Yeah just performance improvements when querying
detman commentedon Feb 26, 2016
imo, there is no need for performance tuning at this point. this should be done when performance sucks on aggregating.
Digitalin commentedon Jul 21, 2016
Hello,
As struct plugin wants to redesign the Data plugin, and after viewing this short but clever video on Database Normalization, I wonder if a type for Primary Key and Foreign Key are not necessary. In one hand, this brings complexity to users but in other hand, thinking a database is an important step to keep it consistent, light, robust and fast in the time. It could be optional with a warning (you know what you do) but it can be seen also as a progressive learning: you can use struct plugin without and it is going to do well but with this option, you get more. And if the mockup of database relation #120 is convincing ;-), it could be not so hard to create relation between tables, even if a deep understanding for this kind of none trivial problem need time and experience.