[fdo][FDO353][New] ApplySchema tries to add unique constraints on identity prop...

Brent Robinson brent.robinson at autodesk.com
Tue Dec 19 17:37:05 EST 2006


You can view the artifact detail at the following URL:

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

Type
 Defect

Artifact ID
 FDO353 (ApplySchema tries to add unique constraints on identity properties.)

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

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

- Steps to Reproduce set to new value
  - Perform an FdoFeatureSchemaCollection::ReadXml() on the attached XML file.

- Perform an ApplySchema, using the 1st feature schema from the above collection


- Defect Severity set to new value
  High
- Target milestone set to new value
  3.2.1
- Description set to new value
  A Feature Schema class can have a unique constraint that exactly contains the class identity properties. If the feature schema is passed to ApplySchema then ApplySchema will try to create the unique constraint. However, some RDBMS's do not allow a unique constraint to have the exact same columns as the primary key for the constraint's table. The RDBMS providers map identity properties onto primary key columns.
- Artifact Status set to new value
  New
- Component set to new value
  RDBMS
- Platform set to new value
  All
- Priority set to new value
  P2
- Artifact created
- Version set to new value
  V2
- Operating system set to new value
  All
- Summary set to new value
  ApplySchema tries to add unique constraints on identity properties. 
- Subcomponent set to new value
  SCHEMA

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








More information about the Fdo_issues mailing list