Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><a href="https://stackoverflow.com/questions/772035/searching-clearcase-for-a-checkin-with-a-specific-comment/772096#772096">Brian Agnew</a> is on the right track, but a word of caution:</p> <ul> <li>I am sure the second command line is NOT needed (<code>cleartool find . -version !"lbtype(LABEL_NAME)"...</code>)</li> <li>'<code>cleartool find -all</code>' is useful if you think that your file may have been moved, but on a big VOB, that process can be extra long</li> <li>without the '<code>-nvis</code>' option, it won't find the file if it has been 'rmnamed' (removed)</li> <li>using '<code>lshistory -minor</code>' is <strong>sheer madness</strong>: on a vob with a few months or years of history, it will simply take too much time. For each element found, it would display the ALL history for <em>all</em> versions of that element, without any possibility to refine that set of versions displayed. That solution simply does not scale.<br> That, and the <code>-minor</code>option of the '<code>lshistory</code>' command does not bring any value to the problem at hand: it would only display the <em>same</em> version <em>several</em> times, just because of internal comments like '<code>Attached hyperlink "Change@13707xx@\my_pvob</code>"' or '<code>Attached hyperlink "Merge@xxxx@\my_vob"</code>'</li> </ul> <p>You need to refine your query with:</p> <ul> <li>the type of element wanted (if it is a file: <code>-type f</code>)</li> <li>the date "<code>created_since(30-Jan)&amp;&amp;!created_since(28-Feb))</code>" for instance would limit the date range to consider</li> <li>the user</li> </ul> <p>I would use:</p> <pre><code>M:\my_base_view\my_base_vob&gt; cleartool find -all -type f -user myLogin -version "{created_since(30-Jan)&amp;&amp;!created_since(28-Feb)}" -exec "cleartool descr -fmt \"%n\t%c\n\" \"%CLEARCASE_XPN%\"" &gt;c:\output.txt </code></pre> <p>That would only look for files checked-in by me for a certain date period, which is a way to have a smaller set of versions to examine.</p> <p>Note that I use '<code>descr</code>' (the <code>describe</code> command) which is only for the <em>current</em> version (and not for displaying the all history of an element like '<code>lshistory</code>' does).</p> <p>If your file has been rmnamed, run again the same command with the '-nvis' option (it would only find elements, along with their branches and versions, that are not visible (do not have a standard path name) in the view.</p> <p>Warning: if you specify a "before" date with a day "in the future" (for instance: '<code>&amp;&amp;!created_since(28-Apr)}</code>' whereas we are not the 28th of April yet), it will always select 0 versions (!?).<br> This is not relevant for your issue, but if you enter a "wrong before date" by mistake, that can lead to the false impression that there is no version to find, where there actually are versions to be found.</p>
    singulars
    1. This table or related slice is empty.
    1. POSearching ClearCase for a checkin with a specific comment
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USVonC
    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. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COYes. I think the above is a good addendum. The example in the IBM notes doesn't concern itself with who made the original checkin, and so you can further optimise.
      singulars
      1. PO
      1. USBrian Agnew
 

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