[fdo-users] "Property RevisionNumber is not user modifiable "
with IInsert command
brent.robinson at autodesk.com
Mon May 30 09:29:06 EDT 2011
You can probably work around this one when you catch the exception, by checking the property value collection passed to the IInsert. If one of the values is named RevisionNumber, then removing it should allow the 2nd insert to succeed.
If the above works, then it's worth logging a defect in Trac. The provider handles RevisionNumber internally and temporarily adds it to the property value collection when the insert is executed. However, when it hits the exception, the cleanup step to remove it is probably being skipped.
From: fdo-users-bounces at lists.osgeo.org [mailto:fdo-users-bounces at lists.osgeo.org] On Behalf Of Ray
Sent: Friday, May 27, 2011 11:14 AM
To: fdo-users at lists.osgeo.org
Subject: [fdo-users] "Property RevisionNumber is not user modifiable " with IInsert command
I have a feature class/ table with unique index defined. Now I use FDO
IInsert command to insert a row which conflicts the unique index. I first
got "Unique constraint" exception. But then I catch the exception to
reassign with a unique value, then execute the IInsert command. I got
exception: "Property RevisionNumber is not user modifiable ". That basically
means I can not insert any unique values again.
How could I skip that exception or avoid the exception ""Property
RevisionNumber is not user modifiable "?
View this message in context: http://osgeo-org.1803224.n2.nabble.com/Property-RevisionNumber-is-not-user-modifiable-with-IInsert-command-tp6411442p6411442.html
Sent from the FDO Users mailing list archive at Nabble.com.
fdo-users mailing list
fdo-users at lists.osgeo.org
More information about the fdo-users