[Tile-serving] [openstreetmap/osm2pgsql] Flex backend: hstore column for all flex tables (#1109)

[mboeringa]

> because the column would still have to be filled, **and there is no sensible way to come up with a default fill for that column**

@joto, as @gravitystorm pointed out, there is already a couple of options in the current osm2pgsql, so I don't completely understand your remark, unless it refers to complex tag transfers involving relations.

Personally though, I would be fine with the option **--hstore** only, because that option inserts minimal tagging information in the hstore column, thus minimizing storage overhead, while maintaining the full tagging information in combination with the non-hstore ordinary columns.

> But it _is_ a strong opinion on how the table should look. Many tables won't need it.

I hope it is still allowed to have an opinion here ;-)

As to "many tables won't need it": this still is looking from the limited perspective of the style developer itself. Any downstream data user may actually desire to have access to other tag information, while still not wanting to develop their own style. 

There is more uses to the current 'openstreetmap-carto' or other style driven databases than just rendering tiles for the web.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/osm2pgsql/issues/1109#issuecomment-610308906
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tile-serving/attachments/20200407/618ffc48/attachment.htm>