I suggest normalizing data table further into additional tables region, energy_vector and technology.
With following relations and columns:
region:
m:n relation to data table via data_region table
columns: id, name
energy_vector:
2x 1:n relation to data table columns input_energy_vector_id and output_energy_vector_id
columns: id, name
technology:
1:n relation to data table column technology_id
columns: id, technology, technology_type, parameter_name
This would lead to improved DB structure and smaller table data.
The user would not "feel" new structure, as the concrete format can be used as interface.
Additionally, checking for already existing data entries should be faster, improving uploading of new data via new relation format (m:n).
On the other hand, normalization format becomes a bit more unwieldy.
henhuy
commented
2 years ago
I suggest normalizing data table further into additional tables
region,energy_vectorandtechnology. With following relations and columns:region: m:n relation to data table viadata_regiontable columns:id,nameenergy_vector: 2x 1:n relation to data table columnsinput_energy_vector_idandoutput_energy_vector_idcolumns:id,nametechnology: 1:n relation to data table columntechnology_idcolumns:id,technology,technology_type,parameter_nameThis would lead to improved DB structure and smaller table data. The user would not "feel" new structure, as the concrete format can be used as interface. Additionally, checking for already existing data entries should be faster, improving uploading of new data via new relation format (m:n). On the other hand, normalization format becomes a bit more unwieldy.