joto created an issue (osm2pgsql-dev/osm2pgsql#2416)
Normal osm2pgsql tables have an id column and osm2pgsql make sure to delete
objects from them if those objects are deleted or changed. But this is not
always the case, especially with the new delete callbacks.
The current way to handle this is to not set a "magic" id column, but add an id
column manually that osm2pgsql doesn't know about. But that seems
counterintuitive and osm2pgsql will also print a warning about an id-less table.
I see two options:
1. Add some option to the `ids` setting when creating the table, something like
auto_delete=off or so.
2. Add explicit `id` types to other types such as `int`, so that osm2pgsql can
know that those special types are used as ids and remove the warning.
--
Reply to this email directly or view it on GitHub:
https://github.com/osm2pgsql-dev/osm2pgsql/issues/2416
You are receiving this because you are subscribed to this thread.
Message ID: <osm2pgsql-dev/osm2pgsql/issues/[email protected]>
_______________________________________________
Tile-serving mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/tile-serving
