[mapguide-users] Re: Item X is already in this named collection

[Brent Robinson]

Hi,

There is a PostgreSQL provider connection tester at http://download.osgeo.org/fdo/3.5.0/tools/. It's available for Windows 32 or 64 bit, with a separate zip file for each. If your MapGuide server is on Linux, I could look into putting together a tester for it. To install, just unzip into a new directory on the same machine as your MapGuide server and follow the instructions in the README file. Hopefully, it will also fail to connect but with a more descriptive error message.

The PostgreSQL provider has also been fixed to provide a better message on connect failure but it'll be a while before the fix shows up in a release.

Brent.


-----Original Message-----
From: mapguide-users-bounces at lists.osgeo.org [mailto:mapguide-users-bounces at lists.osgeo.org] On Behalf Of Marie-Eve Gauthier
Sent: Monday, July 05, 2010 11:32 AM
To: 'MapGuide Users Mail List'
Subject: RE: [mapguide-users] Re: Item X is already in this named collection

Hello Jackie,

I tried to use the OSgeo. PostGreSQL providers but I get this error message:
An exception occurred in FDO component.
RDBMS: Not connected to the specified database.

I didn't change the feature source before I created the layer, so I don't
think that is the problem for the OSgeo.PostGIS provider.

I would like to use the new provider, but it doesn't work at all for now and
I don't know how to make it work! If you have any other tricks, I will be
more than happy.

Marie-Eve Gauthier
All-Can Engineering & Surveys (1976) Ltd.
Phone: 403.244.2131 Ext 281

-----Original Message-----
From: mapguide-users-bounces at lists.osgeo.org
[mailto:mapguide-users-bounces at lists.osgeo.org] On Behalf Of Jackie Ng
Sent: Monday, July 05, 2010 7:10 AM
To: mapguide-users at lists.osgeo.org
Subject: [mapguide-users] Re: Item X is already in this named collection


Although OSGeo.PostGIS and OSGeo.PostgreSQL are both FDO providers for
PostGIS databases. They are implemented differently and as a result:

 - They require different connection parameters
 - They have different naming conventions for schemas/classes/properties.
What this means is that your PostGIS layers will probably break if you
change your feature source from OSGeo.PostGIS to OSGeo.PostgreSQL or vice
versa.

Also note the general consensus is that OSGeo.PostGIS has been really
unreliable for production use, and if possible you should use the
OSGeo.PostgreSQL provider which is newer and will be getting more attention
from Autodesk.

- Jackie
-- 
View this message in context:
http://osgeo-org.1803224.n2.nabble.com/Item-X-is-already-in-this-named-colle
ction-tp5237836p5256002.html
Sent from the MapGuide Users mailing list archive at Nabble.com.
_______________________________________________
mapguide-users mailing list
mapguide-users at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-users


_______________________________________________
mapguide-users mailing list
mapguide-users at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-users