[fdo][FDO214][New] Schema Reverse-Engineering fails if foreign key named the sa...

[Brent Robinson]

You can view the artifact detail at the following URL:

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

Type
 Defect

Artifact ID
 FDO214 (Schema Reverse-Engineering fails if foreign key named the same as column.)

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

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

- Summary set to new value
  Schema Reverse-Engineering fails if foreign key named the same as column.
- Subcomponent set to new value
  SCHEMA
- Steps to Reproduce set to new value
  - Create a MySql database without FDO MetaSchema

- Create table1 with single primary key unsigned int column named "id" (use InnoDB storage engine )

- Create table2 with single primary key unsigned int column named "id", plus another unsigned int column called "table1_id" (use InnoDB storage engine)

- Add foreign key named table1_id to table2 with columns table2.table1_id and table1.id

- Open the datastore in FDO and did a DescribeSchema.

The DescribeSchema fails with a duplicate entry 'table1_id" message.


- Artifact created
- Version set to new value
  V2
- Artifact Status set to new value
  New
- Platform set to new value
  All
- Operating system set to new value
  All
- Description set to new value
  Performing a DescribeSchema, on a MySQL datastore without MetaSchema, fails if a table has a column and foreign key with the same name.

An exception with "duplicate entry" message is thrown.
- Component set to new value
  RDBMS
- Defect Severity set to new value
  High

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