Format

             { FIELD                   }
             { RECORD                  }
      MERGE  { FILE_ELEMENT  type-name }  destination-name  WITH  source-name
             {                         }
             { GENERIC  type-name      }

1  –  Parameters

1.1  –  type-name

    Specifies the type of the file or generic element you are
    merging.

1.2  –  destination-name

    Specifies the name of the merged version.

1.3  –  source-name

    Specifies the name of the branch line version to be merged.

2  –  Description

    The MERGE command creates a merge relationship between a branch
    line version and a new version on the originating line of
    descent. Both versions must be controlled.

    If the versions are of type MCS_TEXT, CDO also performs a
    physical merge that incorporates the highest versions on both
    lines of descent. If the versions are of another type, you must
    perform the physical merge yourself with an editor appropriate to
    your system. If you are familiar with the Oracle CDD/Repository
    callable interface, you can write a method to perform the
    physical merging.

    When you issue the MERGE command, your collection must include
    the version on the originating line, rather than the version
    on the branch line. If your collection includes the branch line
    version, issue the DETACH FROM COMPOSITE and ATTACH TO COMPOSITE
    commands to attach to the highest version on the originating
    line. You must reserve this version before you issue the MERGE
    command.

3  –  Examples

  CDO>  RESERVE FILE_ELEMENT MCS_TEXT JULY_REPORT(2)
  CDO>  MERGE FILE_ELEMENT MCS_TEXT JULY_REPORT(3)
  cont>   WITH JULY_REPORT(1:DRAFT:2)
  CDO>  REPLACE FILE_ELEMENT MCS_TEXT JULY_REPORT(3)

      In this example, the MERGE command creates a relationship
      between JULY_REPORT(1:DRAFT:2) on the branch line and JULY_
      REPORT(3) on the main line. Because JULY_REPORT is of MCS_TEXT
      type, the MERGE command also physically merges the contents of
      JULY_REPORT(1:DRAFT:2) and JULY_REPORT(2) in JULY_REPORT(3).