This is expected behavior. I believe the user has to execute separate calls
against connections to the data that do not contain the joins. Of course the
data can't have open concurrent connections and still allow the update, at
least in cases like SDF.
You should also check to see that you have connection pooling disabled for SDFs
if you plan to update them. Unfortunately this means all SDF connections will
behave slower because the connections aren't cached.
I've have theorized that making a copy of the SDF provider entry in the
providers.xml file and renaming it to indicate it is for update use might help
improve performance.
Any SDF connection that requires updates could use the new "Update" provider
name. Any SDF not requiring update could use the standard provider.
In the serverconfig.ini only disable connection pooling for the "Update"
provider. Of course you shouldn't create two feature sources to the same SDF
using both providers. For this to work you can only use an SDF with one of the
providers otherwise you will have locking issues.
For example make a copy of the following entry:
<FeatureProvider>
<Name>OSGeo.SDF.3.3</Name>
<DisplayName>OSGeo FDO Provider for SDF </DisplayName>
<Description>Read/write access to Autodesk's spatial database format, a
file-based personal geodatabase that supports multiple features/attributes,
spatial indexing, and file-locking. </Description>
<IsManaged>False</IsManaged>
<Version>3.3.0.0</Version>
<FeatureDataObjectsVersion>3.3.0.0</FeatureDataObjectsVersion>
<LibraryPath>SDFProvider.dll</LibraryPath>
</FeatureProvider>
<FeatureProvider>
<Name>OSGeo.SDF_Update.3.3</Name>
<DisplayName>OSGeo FDO Provider for SDF Updates </DisplayName>
<Description>Read/write access to Autodesk's spatial database format, a
file-based personal geodatabase that supports multiple features/attributes,
spatial indexing, and file-locking. </Description>
<IsManaged>False</IsManaged>
<Version>3.3.0.0</Version>
<FeatureDataObjectsVersion>3.3.0.0</FeatureDataObjectsVersion>
<LibraryPath>SDFProvider.dll</LibraryPath>
</FeatureProvider>
When the second provider name is selected from the list the generic feature
source connection editor will be used in MapGuide Studio.
Simply name your connections to include _update or _UPD to help identify which
ones are for update purposes.
Regards,
Dave
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mbonnet
Sent: Thursday, August 07, 2008 2:35 AM
To: [email protected]
Subject: [mapguide-users] Update Joined layer feature
Hi,
I have created a joid layer (SDF - Oracle or SQL Server) but when i whant to
update a feature (ADD, DELETE, UPDATE) on this layer it doesn't work, when i
delete the join (only sdf) it works with the same code, is it normal.
--
View this message in context:
http://www.nabble.com/Update-Joined-layer-feature-tp18866208p18866208.html
Sent from the MapGuide Users mailing list archive at Nabble.com.
_______________________________________________
mapguide-users mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/mapguide-users
_______________________________________________
mapguide-users mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/mapguide-users
