We are upgrading from BM for MicroStation SS2 to SS4 using Oracle Spatial.
We have line feature (Textstege_Line) with two point sub features (Textstege_Text, Textstege_Cell).
When we register them i SS2 we are asked to add Id Generators for both sub-features (which we have). In SS4 we are only asked to add Id Generators for the main features.This result in the primary ID column for the sub-features are listed as a property. We can read Everything just fine, but the features cannot be posted back in SS4.
The primary and foreign key is defined as follows for the sub-features:
alter table TEXTSTEGE_TEXT add constraint TEXTSTEGE_TEXT_PK primary key (ID);
alter table TEXTSTEGE_TEXT add constraint TEXTSTEGE_TEXT_FK foreign key (TEXTSTEGE_ID) references TEXTSTEGE_LINE(ID) on delete Cascade;
No ideas?
/Kristers
Owner consultant at Surell Consulting AB
Hi Krister. I took a look at your reported problem and I have not been able to reproduce what you are seeing. I have a similar subfeature table defined with a PK and FK to a spatial feature table, but I see Map registering the feature as expected. The Geospatial Administrator prompts for two sequences. Could you possibly provide a simple SQL test case to show the issue? Your PK and FK assignments look fine. Perhaps if I saw your table creation SQL as well this would shed some light?
Thanks for looking into this!
Right now I've got it working by manually editing the xml-file. Removing the ID-property from the sub-features and adding it to the ECproperties including the sequence.
But if I need to re-register it will get corrupt again so I will try to send you some data. I need to check first since this is part of a classified system.
I'll be back!
/Krister
Hi again,
Sorry about the delay.
Now I have some files that shows how the feature is set up and also two xml-extracts that shows the registred feature and the edited working feature.
Please have a look and see if you can spot the problem.
Regards,
Krister
To_Bentley.zip
Hi Krister
Thanks for the data set. This looks like it may be an issue and we are reviewing it now. I'll keep you up to date with our findings.
Thank you
Mark