[OSM-dev] Very long ways have been split (was: Status of Database Server after 0.4 Upgrade: Fragile)

lizard lizard at furcon.de
Mon May 14 17:04:06 BST 2007

what is the real problem of very long ways?
load of preparing data for download?
if yes, whats about caching?
simply cache the output of long ways in a table (pahaps repared
xml-style) and simply delete them while updating (or update
directly) ... so the way would only be regenerated if it was changed 


More information about the dev mailing list