|Title||Replicating some fields can break Bugzilla|
|Assigned user||Nick Barnes|
|Description||Some fields can not be changed using the Bugzilla interface, or only changed in highly restricted ways. Now that these fields can be replicated into Perforce, we should restrict changing these fields in Perforce.|
For instance, the 'votes' field can only be changed by voting, which involves checking and updating other fields in other tables and may have other side-effects.
For another instance, the 'product', 'version', and 'component' fields must be keys into other tables.
For a third instance, the created_ts field is never updated.
|Analysis||This probably involves having a list of fields which must not be updated from Perforce. If the replicator tries to update one of these fields, it should fail with a meaningful error message.|
|Evidence||I just know|
|Created by||Nick Barnes|
|Created on||2001-01-11 15:45:46|
|Last modified by||Gareth Rees|
|Last modified on||2001-12-10 19:18:03|
|History||2001-01-11 NB Created.|
2001-02-19 GDR Downgraded to essential.
|7052||closed||2001-01-12 16:21:55||Nick Barnes||Added longdesc support.|
|7021||closed||2001-01-11 16:22:02||Nick Barnes||Prevent changes to a set of 'read-only' fields.|