[fdo-internals] PATCH: Connection-Properties of various providers

[Traian Stanev]

====
OGR:
Here I am not sure and didn't change anything so far. 
Currently IsEnumerable is set to false. Why does the OgrProvider not handle this like the SDF-Provider does?
====

Because setting it to true breaks the default FDO connection dialog in Map3D -- at least it did when I first wrote it. SDF uses a custom FDO connection dialog,  which works.

Traian


-----Original Message-----
From: fdo-internals-bounces at lists.osgeo.org [mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Aaron Pieler
Sent: Monday, April 06, 2009 9:14 AM
To: fdo-internals at lists.osgeo.org
Subject: [fdo-internals] PATCH: Connection-Properties of various providers

Hello everyone,

In an attempt to unifiy the behaviour of the connection properties i made
following changes to the providers:

ODBC:
* DataSourceName: IsRequired = true
* ConnectionString: IsRequired = true
* GenerateDefaultGeometryProperty: IsEnumerable = true; EnumerableValues=
true, false

SHP:
* DefaultFileLocation: IsRequired = true

WFS, WMS, King-Oracle:
* Password: IsProtected = true;

SQL Server Spatial:
* ConnectionString:  IsProtected == false (Why is the ConnectionString
currently handled like a password? Is this really necessary?)

OGR:
Here I am not sure and didn't change anything so far. 
Currently IsEnumerable is set to false. Why does the OgrProvider not handle
this like the SDF-Provider does?


Does someone have an objection against something or comments about
something?
Would these changes do harm to applications currently using FDO?

Thanks





_______________________________________________
fdo-internals mailing list
fdo-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/fdo-internals