Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>"Safely" is probably an important point here. Once you rename or move the file it'll get a revision number of "1" which looks like a new file to your Perforce client. Of course, admins will be able to get its prior history, but if the editing/version history of the file is important to you it's a little harder to get the older revision.</p> <p>Update: Thanks to Commodore Jaeger and Greg Whitfield for enlightening comments.</p> <p>This wasn't easy to track down regarding what the One True Answer is, even from Perforce support, so I figured I'd update everyone on what we found:</p> <ul> <li>Perforce stores all versions of every document in its database.</li> <li>If it's saving your file as type "" or "" then it stores the diffs of one file version to another and not the entire file. </li> <li>If you check out a file, make no changes to it, and then re-submit, it will save as a new version with 0 diffs. This is configurable and P4 can be set up to ignore changelist items without any actual diffs. You can force this behavior by selecting "Revert unchanged files..." before you submit a changelist. </li> <li>Use "Rename/Move..." to move files in P4 so it can track them. Don't copy them using Windows Explorer and then re-add them in P4. </li> <li>If you use the "Rename/Move..." function from the context menu, the "new" file will show a revision number of "1" as though it were a new file. </li> <li>However, since P4 saves every function performed on a file, you can actually get to any previous revision (and even recover "deleted" files) with the CLI command "p4 filelog -i" </li> <li>If you want to get to the revision history of a moved or renamed file and you're not an admin, you can right-click and select its "Revision Graph" which shows every version of a file even when moved between branches.</li> </ul> <p>According to Perforce support, easier tracking of revision history through branch or folder moves is an oft-requested feature and is in their current roadmap.</p> <p>Perforce's answer: At the moment, there isn't a way to move/rename/integrate files and still maintain the exact file history.</p> <p>However, if you were to choose "Integrate..." by right-clicking on the folder that you want to share, the versions of the files of the newly branched folder and underlying files will start from revision #1, but the integration history between the branched folder and underlying files and the original folder and underlying files will remain through which you can trace the revision history of the files.</p>
    singulars
    1. This table or related slice is empty.
    1. POCan I safely edit a renamed file in perforce
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USJough Dempsey
    1. USJough Dempsey
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTDownMod
    1. COPerforce tracks moved files (assuming you move the file within perforce instead of deleting it and copying it without Perforce's knowledge), and it's pretty easy to get the history of the file before the move using p4 filelog -i.
      singulars
      1. PO
      1. USCommodore Jaeger
    2. CODownscored as this "major flaw of Perforce" is not true. As Jaeger states, Perforce retains the history of renamed files correctly. If you're not comfortable with the command line, in P4V/P4Win there's a checkbox to see revisions across branch operations (which includes rename)
      singulars
      1. PO
      1. USGreg Whitfield
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload