Hi, I'm writing this mail to get some preliminary feedback on the idea of adding, on trunk only, a DataAccess.dropSchema(Name typename) and a DataStore.dropSchema(String typename) methods allowing the users not only to create and update schemas, but also to drop them.
If a datastore decides not to support the methods it will just throw an UnsupportedOperationException. The changes I have in mind will make so that the base classes we have (AbstractDataStore, ContentDataStore) just throw an exception, which should cover pretty much the whole code base with the exception of the app schema store, and then provide a simple drop table implementation for JDBC-NG datastores. How do people feel about this? It is an API break for datastore implementors, but an easy to fix one and it will hit only whoever implemented the stores directly from the interfaces (daunting, I doubt it will actually affect many people). If there are no strong objections I'll go and prepare a proposal for this. Cheers Andrea -- Andrea Aime OpenGeo - http://opengeo.org Expert service straight from the developers. ------------------------------------------------------------------------------ _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
