Hi, Tom Hughes wrote: > It's a completely insane solution though. It we want to do it we should > just do it properly in the database not fart around with stupid hacks in > the rails code that break as soon as any updates are not done via rails.
Assuming for a moment that the database was our bottleneck, something that can be done by "farting around" on a number of easily scalable API servers would of course compare favourably to burdening the not-so-scalable database with triggers and extra write operations, would it not? Now I don't know how often you manually modify database contents, but I would think that any operation of a scale that would lead us to bypass the rails API would also be very likely to blow apart anyone who listens for edits downstream, so in my eyes there's not much to be gained by streaming these "manual override" kinds of edits as well. Bye Frederik -- Frederik Ramm ## eMail [email protected] ## N49°00'09" E008°23'33" _______________________________________________ talk mailing list [email protected] http://lists.openstreetmap.org/listinfo/talk
