Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Motivation:

Complete the schema management API with a remove schema call

Contact:

full name

Tracker:

http://jira.codehaus.org/browse/GEOT-XXXX

Tagline:

We add, we update... we don't remove?

Description

The current DataAccess/DataStore API provides means to create and update a schema, but not a way to remove it.
The DataAccess interface will be modified as follows:

Whilst the DataStore interface will see the following new method:

The code base will be modified, on trunk only, so that the new methods are implemented by throwing an UnsupportedOperationException in the common base classes, and making sure all the code base keeps on building.
Moreover, the support to actually drop the schemas will be implemented in the JDBC data stores.

Status

This proposal was approved, but has been on hold waiting funding:

Tasks

This section is used to make sure your proposal is complete (did you remember documentation?) and has enough paid or volunteer time lined up to be a success

 

no progress

(tick)

done

(error)

impeded

(warning)

lack mandate/funds/time

(question)

volunteer needed

  1. DataStore API changed based on BEFORE / AFTER
    1. Unsupported Operation for ContentDataStore and AbstractDataStore
  2. Implement for JDBCDataStore using drop table
    1. Individual Dialects may need additional hooks to allow for spatial index maintenance, geometry columns and so on
  3. User Guide - datastore code example
  4. Backport JDBCDataStore implementation to stable series
  • No labels