Opened 18 years ago

Closed 18 years ago

#28 closed defect (fixed)

MySQL: cannot insert into or update foreign schema class via FDO gateway

Reported by: brentrobinson Owned by: brentrobinson
Priority: major Milestone: 3.3.0
Component: MySQL Provider Version: 3.2.0
Severity: 2 Keywords: foreign schema insert
Cc: External ID:

Description

  • created a non-FDO datastore with a single table with the following columns:

id varchar(20) not null. data varchar(50) null, geometry geometry, primary key(id)

  • created an FDO datastore and applied a Feature Schema and schema overrides that relate a feature class to the above table.
  • executed a FdoIInsert command against the feature class. Got the following exception:

No column for property 'ClassId'

Change History (2)

comment:1 by brentrobinson, 18 years ago

Status: new → assigned

comment:2 by brentrobinson, 18 years ago

Resolution: → fixed
Status: assigned → closed

Modified the FdoIInsert and FdoIUpdate implementations for MySQL Provider to ignore system properties that don't have columns. This allows the MySQL Provider to handle tables without classid or revisionnumber columns, when these tables are accessed via an FDO datastore.

Revision: 2643 Author: brentrobinson Date: 5:24:22 PM, Monday, March 05, 2007 Message: Ticket #28: Merged Revision 777 from branch 3.2.x: Handle missing system properties for externally created tables.

Modified : /trunk/Providers/GenericRdbms/Src/Fdo/FeatureCommands/FdoRdbmsInsertCommand.cpp Modified : /trunk/Providers/GenericRdbms/Src/Fdo/FeatureCommands/FdoRdbmsUpdateCommand.cpp Modified : /trunk/Providers/GenericRdbms/Src/Fdo/Pvc/FdoRdbmsPvcInsertHandler.cpp Modified : /trunk/Providers/GenericRdbms/Src/Fdo/Pvc/FdoRdbmsPvcUpdateHandler.cpp

Note: See TracTickets for help on using tickets.