search

GispoCoding / tarmo

Tarmo - Tampere Mobilemap
https://ulkoilutampereenseutu.fi/
MIT License
11 stars 3 forks source link

Use materialized views in kooste schema #13

Open Joonalai opened 2 years ago

Joonalai commented 2 years ago

Use materialized views in kooste schema to make it easier to update rows.

SannaJokela commented 2 years ago

@pavetsu14 do we need original LIPAS tables?

pavetsu14 commented 2 years ago

@SannaJokela Not necessarily.

But by storing the original tables in the lipas schema as they are served in Lipas system creates additional knowledge. E.g. if we have an object belonging to luistelukenttä class in the lipas_pisteet table in the kooste schema, we do not really know what kind of attribute data there is available from this kind of objects in Lipas. This follows from the fact that different kind of attribute data gets acquired from sport places with different type codes and in the kooste schema, we only have taken an union of all possible attribute data collected from any of the sport places' type codes we are interested in. So if luistelukenttä object has null on toilet-field, without lipas schema, we have no way of knowing whether this information is missing just from this particular object or whether it is not possible to store for objects belonging to luistelukenttä class at all.

SannaJokela commented 2 years ago

@pavetsu14 is this still an issue? Can you close this or assign to Riku.

pavetsu14 commented 2 years ago

@SannaJokela This might be an issue, depends on whether performance problems emerge. Would be an improvement, but probably not a necessary change