Re: [OSM-dev] Potlatch - really BAD bug

2009-01-21 Thread Matthias Julius
Eddy Petrișor writes: > So, AIUI, even JOSM or any other sw that works with relatively high > loads of data at a time could bring up the same behaviour? The standard API does not allow you to delete a node that is still referenced by a way. Therefore, this type of problem should not be possible

Re: [OSM-dev] Potlatch - really BAD bug

2009-01-13 Thread Dave Stubbs
2009/1/13 "Marc Schütz" : >> Diff uploads will not help online editor such as Potlatch. The >> addition of transactions and exposure of the version numbers will help >> more. > > Why not? It may well utilize it for changes to multiple objects that should > be atomic, e.g. the example mentioned her

Re: [OSM-dev] Potlatch - really BAD bug

2009-01-13 Thread Marc Schütz
> Diff uploads will not help online editor such as Potlatch. The > addition of transactions and exposure of the version numbers will help > more. Why not? It may well utilize it for changes to multiple objects that should be atomic, e.g. the example mentioned here. Regards, Marc -- Pt!

Re: [OSM-dev] Potlatch - really BAD bug

2009-01-13 Thread Shaun McDonald
On 13 Jan 2009, at 12:14, Marc Schütz wrote: >>> It has been explained many times in the >>> past, not just >>> by me, that database freakiness _will_ happen because we don't >>> have >>> transactions, our server is often under high load, and there >>> may be memory >>> leaks or blocking processe

Re: [OSM-dev] Potlatch - really BAD bug

2009-01-13 Thread Shaun McDonald
On 13 Jan 2009, at 09:22, Ed Loach wrote: > Richard wrote: > >> It has been explained many times in the >> past, not just >> by me, that database freakiness _will_ happen because we don't >> have >> transactions, our server is often under high load, and there >> may be memory >> leaks or blocking

Re: [OSM-dev] Potlatch - really BAD bug

2009-01-13 Thread Marc Schütz
> > It has been explained many times in the > > past, not just > > by me, that database freakiness _will_ happen because we don't > > have > > transactions, our server is often under high load, and there > > may be memory > > leaks or blocking processes in some of the software we use. > > Do I un

Re: [OSM-dev] Potlatch - really BAD bug

2009-01-13 Thread Eddy Petrișor
Richard Fairhurst a scris: > D Tucny wrote: >> Eddy Petrișor wrote: >>> What's even more weirder is the fact that if I try to edit with >>> Potlatch, the way is displayed correctly, as if stale data was read of >>> as if Mapnik's data was read. >>> [...] >> There was a post 12 hours ago to the tal

Re: [OSM-dev] Potlatch - really BAD bug

2009-01-13 Thread Ed Loach
Richard wrote: > It has been explained many times in the > past, not just > by me, that database freakiness _will_ happen because we don't > have > transactions, our server is often under high load, and there > may be memory > leaks or blocking processes in some of the software we use. Do I unde

Re: [OSM-dev] Potlatch - really BAD bug

2009-01-13 Thread Richard Fairhurst
D Tucny wrote: >Eddy Petrișor wrote: >> What's even more weirder is the fact that if I try to edit with >> Potlatch, the way is displayed correctly, as if stale data was read of >> as if Mapnik's data was read. >> [...] > > There was a post 12 hours ago to the talk list about the exact same > th

Re: [OSM-dev] Potlatch - really BAD bug

2009-01-12 Thread D Tucny
2009/1/13 Eddy Petrișor > Hello, > > We have just seen that a portion of the map I edited yesterday with > Potlatch is now really broken, is missing lots of points and has its > history broken. > > > http://openstreetmap.org/?lat=44.86196&lon=24.89171&zoom=16&layers=B000FTTT > > This is easily vi

[OSM-dev] Potlatch - really BAD bug

2009-01-12 Thread Eddy Petrișor
Hello, We have just seen that a portion of the map I edited yesterday with Potlatch is now really broken, is missing lots of points and has its history broken. http://openstreetmap.org/?lat=44.86196&lon=24.89171&zoom=16&layers=B000FTTT This is easily visible when comparing mapnik and osmarender