[fdo-internals] PostGIS ticket 106 question
robert.fortin at autodesk.com
Wed Feb 20 11:41:48 EST 2008
At first I thought that it was up to the provider to decide in what circumstance a class (table) could be deleted.
Well, not really...
The documentation is not always clear and detailed but in this case the FDO spec for ApplySchema is pretty clear (extract from http://fdo.osgeo.org/files/fdo/docs/FDO_API/index.htm FdoIApplySchema Class Reference)
If schema changes include deletion of classes or the schema itself, then those classes (or the schema, if it is marked as deleted) must not contain any instance data. If they do, an exception will be thrown.
So as soon as there is data you can delete the table. You must empty the table before you can delete it.
From: fdo-internals-bounces at lists.osgeo.org [mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Mateusz Loskot
Sent: Wednesday, February 20, 2008 11:22 AM
To: FDO Internals Mail List
Subject: Re: [fdo-internals] PostGIS ticket 106 question
Bruno Scott wrote:
> As we are about to fix that one
> Just want to check with you guys because there is a debate on that one
> For my point of view, as PostGIS allow dropping table with the SQL "Drop
> table" it's safe to do so.
It should be safe at least in current version of PostGIS provider,
I mean where a feature class mapping to physical table is simple
one-to-one relation, but if in future there is more complex mapping
available then simple DROP TABLE may break data consistency.
fdo-internals mailing list
fdo-internals at lists.osgeo.org
More information about the fdo-internals