On 15 February 2012 06:10, Brett Henderson <[email protected]> wrote: > Hi Simon, > > The relevant error in your full log is below. All other errors in the log > are caused by other threads failing when they can't write to their > destination (ie. the db writing thread is downstream of all other threads). > > > SEVERE: Thread for task 25-buffer failed >> org.openstreetmap.osmosis. > core.OsmosisRuntimeException: Unable to >> insert a new changeset for user with id -1. >> at >> org.openstreetmap.osmosis.apidb.v0_6.impl.ChangesetManager.addChangeset(ChangesetManager.java:160)
8< > There were some changes made to the apidb schema recently where columns > named "id" were renamed to "xxxx_id". For example, the nodes table now > contains a node_id column instead of id column. I'm guessing this is what > is tripping you up. Ah, yes probably. > Do you have to use MySQL? Osmosis still contains the MySQL but it is no > longer tested. All of CycleStreets uses MySQL so abandoning that would require a lot of work. I've learned my way around MySQL now and know what to avoid and what to use. I'd have to go through the same process with Postgres - and we did start down that path a couple of years ago when it looked like you were abandoning MySQL. > It may be necessary to update the MySQL schema to match the > PostgreSQL schema. OK, I might look into that, but I think it is more likely that we'll just stick with 0.39 of Osmosis for the time being. In our MySQL schema all the tables are BLACKHOLE and I use triggers just to catch the cycling specific data. Simon _______________________________________________ osmosis-dev mailing list [email protected] http://lists.openstreetmap.org/listinfo/osmosis-dev
