3. Nov 2018 14:16 by [email protected] <mailto:[email protected]>: > On Sat, Nov 03, 2018 at 01:37:52PM +0100, Mateusz Konieczny wrote: >> 1. Nov 2018 16:30 by >> [email protected] >> <mailto:[email protected]>>> <>> mailto:[email protected] >> <mailto:mailto:[email protected]>>> >: >> >> >> > In both use cases, the major purpose of the foreign key is to avoid manual >> > review in the case where OSM will not be updated. If an object (retrieved >> > by key) is unchanged since the last import, in both OSM and the external >> > database, then there is no work to be done. >> >> Is there some reason why storing "object with id in database XYZ was >> uploaded as OSM object >> with id 717373737" should be stored in OSM? >> >> This data is useful only to whoever made the import and keeps updating data. >> Others, >> even when working with the same data must anyway verify whatever OSM objects >> really match >> objects in the external database. > > So you're suggesting storing the relation between the 2 database > in a 3rd database? > Yes. Though simple text file should be also sufficient. I am still not convinced that this data will be useful to anybody except to single person repeating synchronization from specific database for some time.
_______________________________________________ Imports mailing list [email protected] https://lists.openstreetmap.org/listinfo/imports
