| Title: | System fields like P4DTI-rid are editable by users in Perforce |
| Status: | open |
| Priority: | nice |
| Assigned user: | Nick Barnes |
| Organization: | Perforce |
| Description: | Some fields in the Perforce jobspec should not be edited by the user, for example P4DTI-rid and P4DTI-issue-id. But these are easily editable in the Perforce command line and GUI. We have to depend on people's carefulness. |
| Analysis: | Our requirements are to have fields in jobs that are (a) read-only in normal use (p4 job); and either (b) can be set to anything we like when the job is created; or (c) nonetheless editable in some circumstance (for example, by p4 job -f). Until P4D 2002.2, there was no class of fields in a Perforce job which fitted this description. I thought that "once" fields would be the solution, but in fact "once" fields satisfied (a) but neither (b) or (c). P4D 2002.2 fixed this: "once" fields can be set by "p4 job -f". So we can now fix this by setting our "read-only" fields to be "once" in the P4DTI, then use p4 job -f when setting these fields up for the first time. This has to be conditional on the P4D version in use. |
| How found: | inspection |
| Evidence: | I just know. |
| Observed in: | 0.4.2 |
| Created by: | Gareth Rees |
| Created on: | 2001‑01‑15 13:04:46 |
| Last modified by: | Gareth Rees |
| Last modified on: | 2010‑10‑28 22:04:00 |
| History: | 2001-01-15 GDR Created. 2001-01-18 RB Set priority to "nice". 2003-08-12 NB Updated to reflect new status of "once" fields. |
Generated at 2013-05-22 16:38:25 by $Id: //info.ravenbrook.com/infosys/cgi/issue.cgi#476 $
Copyright © Ravenbrook Limited. This document is provided "as is", without any express or implied warranty. In no event will the authors be held liable for any damages arising from the use of this document. You may make and distribute verbatim copies of this document provided that you do not charge a fee for this document or for its distribution.