On Wed, May 13, 2009 at 7:36 PM, Ian Dees <[email protected]> wrote: > On Wed, May 13, 2009 at 1:33 PM, Matt Amos <[email protected]> wrote: >> On Wed, May 13, 2009 at 7:30 PM, Ian Dees <[email protected]> wrote: >> > On Wed, May 13, 2009 at 1:27 PM, Matt Amos <[email protected]> wrote: >> >> sorry, i wasn't clear in my question: why triggers in particular, >> >> rather than one of the many other features that the DB provides for >> >> doing this? >> > >> > Mostly because it would allow us to use the same XML format that >> > everybody >> > already knows how to parse and because it's what I've worked with in my >> > limited PostgreSQL experience. >> >> why would it allow us to use the XML format? nothing in XML ever goes >> near the database. > > I meant that it would trigger some external executable that would build up > the XML, not that the database would do it.
is the external executable called osmosis? >> > What other features were you thinking about? >> >> i was looking at snapshots and transaction IDs to isolate the updated >> rows in the history tables. > > I yield to your judgment on that. I haven't given myself enough time to > explore abusing the database app for such a thing. its better to get this done without the main db and the rails_port code diverging too much, so i'm looking for methods which are as un-invasive as possible. cheers, matt _______________________________________________ talk mailing list [email protected] http://lists.openstreetmap.org/listinfo/talk
