[Tile-serving] [osm2pgsql-dev/osm2pgsql] Refuse to import data when there is an osm2pgsql_properties table (PR #2085)

[Sarah Hoffmann]

Not sure what to do with this one.

I very much agree that the current bahaviour of osm2pgsql is dangerous and it should rather be conservative about overwriting existing data. But we've had this behaviour for a long time and I'm fully aware that many users rely on it. The properties table does change the game a little bit: you cannot do two imports with different prefixes on the same database anymore without breaking something. That was not the case before. The recommended work-around is to use schemas but, again, we do have some historic baggage here.

If we do change the behaviour, then I'd rather do it without introducing an additional command line. We already have far too many of them and you can simply overwrite the check by running a `psql -d whatever -c 'DROP TABLE osm2pgsql_properties`. Then the user at least knows what they are getting into.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/osm2pgsql-dev/osm2pgsql/pull/2085#issuecomment-1798102811
You are receiving this because you are subscribed to this thread.

Message ID: <osm2pgsql-dev/osm2pgsql/pull/2085/c1798102811 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tile-serving/attachments/20231107/028f0623/attachment.htm>