[OSM-dev] Osmosis Replication Statistics

[Brett Henderson]

Tom Hughes wrote:
> Nothing has been deleted from any table - see my earlier email for
> the details but basically visible was set to 0 in the live tables
> and nothing was done in the history tables.
>   
Sorry, I completely misread that.  Any idea on the best way forward?  I 
can try to come up with a list of offending entities, might take me a 
while though.  From there what is the best way to update the db?  
Presumably uploading via the API is not feasible.  If I can generate a 
change file with all of the entities to be deleted, osmosis can apply a 
change directly to the database.  I'm nervous about osmosis updating the 
main database though because database change application is not well 
tested yet and if it fails halfway through there is no way of rolling 
back or tracking progress (in fact currently it will rollback the InnoDB 
portion and not the MyISAM portion which is far from ideal).  I'd have 
to break it into smaller files before applying to minimise problems.

What timestamps should be applied to the deletes?

I don't know ruby but perhaps there's a quicker way to knock up a script 
that uses current API code to make the required changes.