On Tue, Dec 10, 2013 at 9:43 PM, Jody Garnett <[email protected]>wrote:
> Interesting discussion.
>
> Som ideas:
> - We may be able to use updateSchema with this map of hints to mark which
> attributes need an index created
> - The "Info" objects may be able to report back on what is indexed
> (without disrupting our feature model classes)
>
Mind, there is no intention of expanding these methods outside of the
JDBCDataStores, so I'm not that worried
about having to add an extra class.
About using updateSchema, yep, reasonable idea, but it does not map as well
to the DBMS world imho:
* createSchema -> CREATE TABLE
* dropSchema -> DROP TABLE
* updateSchema -> ALTER TABLE
* createIndex -> CREATE INDEX
* dropIndex -> DROP INDEX
Answering also Justin's mail, roger about dropping the JDBC prefix.
About using add instead of create, I feel create maps better the DBMS
realm, but I'm not attached
to it, I'm good with addIndex too.
Cheers
Andrea
--
==
Our support, Your Success! Visit http://opensdi.geo-solutions.it for more
information.
==
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
-------------------------------------------------------
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
GeoTools-Devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
