On Wed, 26 Nov 2008, Matt Amos wrote: > On Wed, Nov 26, 2008 at 7:54 AM, Stefan de Konink <[EMAIL PROTECTED]> wrote: > > Then let me even get a better proposal; A second machines will be > > installed that has enforced foreign keys. This second machine will produce > > the planet. And will directly trigger events upon corruption so the main > > API doesn't need to cope with them until 0.6. > > it is worth noting that foreign keys and transactions alone will > drastically reduce the number of problems, but may not solve them > entirely. the foreign key from current_way_nodes to current_ways and > current_nodes only ensures that those nodes have existed. the > current_* table stores (as the name suggests) the current state of > entities. that state may be "deleted".
The visible= aspect breaks SQL, and its good features. That was a thing I have also observed and basically, my `workaround' for it is only storing the `real' current nodes opposed to deleted onces, that are obviously not current anymore. Stefan _______________________________________________ dev mailing list [email protected] http://lists.openstreetmap.org/listinfo/dev
