On 31 Jul 2011, at 8:07am, Alexey Pechnikov wrote: > 2011/7/31 Simon Slavin <slav...@bigfraud.org>: >> Right. So if a customer orders one of my products they'll be presented with >> two different costs and pick the one they like. Great system. > > You customers have edit privilegies to you prices?! It's not the > replication problem of cource.
No. My staff can edit my prices. One may edit a price because the company decided to make more profit on the item. And another, working in a different office, may edit a price because a component cost has changed. But according to you ... On 30 Jul 2011, at 11:31pm, Alexey Pechnikov wrote: > 2011/7/31 Roger Binns <rog...@rogerbinns.com>: >> It takes more than a few lines of SQL. You've also got to be careful how >> you write data (result is a DAG), you need replication code and you need >> conflict resolution code. > > There are no conflicts! Two versions are two _different_ versions of the row. ... if two changes are made, the database will maintain both resulting records and return them both when the database is interrogated. And my web-facing sales system is one of the systems that interrogates the database. Multi-copy synchronisation requires conflict resolution. If you don't do it, you don't have data that reflects the real world, you have data that reflects lots of different people's views of the real world. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
