[Tile-serving] [openstreetmap/osm2pgsql] Creating new Schema for OSM data (#768)

[mmd]

This is interesting. I had exactly the opposite argument in mind: by setting the search_path centrally when connecting to the database, any subsequent statement would automatically take this into account, be it when creating indices, or adding/deleting tables entries. Having to take care of an explicit schema name everywhere adds more mental load, and there's some chance someone might simply forget about it in the future. So I'd be interested to find out where you see long term issues. Maybe I'm missing something here.

The one thing I find a bit unfortunate is that we need to add the hstore extension schema name during table creation. This might be different from "public" after all, and we might have to provide some parameter to specify the hstore schema name (which is _public_ by default).

-- 
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/768#issuecomment-554754376
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tile-serving/attachments/20191117/c61d081f/attachment.html>