<Reverse> Element

Specifies that the connection in the many-to-many association is mapped in the reverse direction of the association.

collection-property-name

The name of the collection property on the associated type, representing the same many-to-many association.

Remarks

If both directions of the many-to-many association are implemented, the detailed mapping of the connection must be specified only once for the association. Hence, one of the two collections has to be mapped as the "reverse" counterpart of the other collection by using the <Reverse> element . Note, however, that this constraint is introduced only to ensure consistency of the mapping. It can be freely decided which collection is mapped as the main direction and which as the reverse direction, because it does not imply any difference in the declaration or behaviour of the collections.

Examples

                
  <Type name="Keeper">
      <Member name="Cages ">
          <ManyToManyCollection>
              <Reverse collectionName="Keepers" />
          </ManyToManyCollection>
      </Member>
  </Type>
  
  <!-- The reverse direction of the association must be mapped on the Cage.Keepers collection -->
  <Type name="Cage">

      <Member name="Keepers">
          <ManyToManyCollection>
              <Automatic/>
          </ManyToManyCollection>
      </Member>
      
  </Type>
              

Requirements

Type: TechTalk.Genome.Mapping.ReverseXmlData, TechTalk.Genome.Mapping.ManyToManyCollectionXmlData

Assembly: TechTalk.Genome.dll

Version: 4.2.4

Editions: Professional, Evaluation, Express

Database Platforms: Microsoft SQL Server 2000, Microsoft SQL Server 2005, Oracle 9i Release 2, Oracle 10g Release 2

See Also

<ManyToManyCollection> Element