On Wed, 11 Feb 2009, comex wrote: > If we're going to use a computer analogy, if a proposal is a database > row-- part of the gamestate 'database' it can be changed. The only > way a proposal can't be changed is if it's precisely the sum of its > parts-- a tuple, perhaps, of (text, ai, ii). But that raises the > duplicate-proposal issues before.
Not to push this analogy too far, but if "text+publication message" is the primary key, and AI etc. is not the primary key, changing the text+publication message creates a new record (proposal) but changing the other items doesn't. There's nothing that "breaks" per se with this case and nothing that's counterfactual. -Goethe
