[fdo][FDO241][New] Second constraint lost when deserializing class with 2 uniqu...

[Brent Robinson]

You can view the artifact detail at the following URL:

    https://fdo.osgeo.org/servlets/Scarab/id/FDO241

Type
 Defect

Artifact ID
 FDO241 (Second constraint lost when deserializing class with 2 unique constraints from XML.)

Reported by
 Brent Robinson
 brentrobinson (brent.robinson at autodesk.com)

New artifact details:
---------------------------------------------------------

- Summary set to new value
  Second constraint lost when deserializing class with 2 unique constraints from XML.
- Operating system set to new value
  All
- Artifact created
- Platform set to new value
  All
- Priority set to new value
  P2
- Defect Severity set to new value
  High
- Version set to new value
  V2
- Component set to new value
  FDO
- Artifact Status set to new value
  New
- Steps to Reproduce set to new value
  - start with a XML Schema file with a class that has 2 unique constraints
- deserialize the file using FdoFeatureSchemaCollection::ReadXml
- Open a connection with the Oracle Provider and apply the feature schema that was read to the opened datastore.

Only the second constraint makes it into the datastore
- Description set to new value
  When a class with 2 unique constraints is read from XML, the first constraint becomes empty (no properties).

This is a regression from some fdo\Schema\MergeContext.cpp changes made in August 2006.
- Subcomponent set to new value
  XML IN/OUT

---------------------------------------------------------
This message was automatically generated by Project Tracker.