Justin Deoliveira ha scritto: > I wonder if we really need an interface? Could we just roll support for > a primary key metadata table into the regular lookup chain? What sorts > of alternative strategies might be used?
I'm not sure actually, but someone might not want to pollute their schema with a GT2 lookup table and keep stuff somewhere else. Anyways, doing it directly in the JDBCDataStore is easy enough and less work for me. Let's do it there, directly, and if the necessity arises that we need to make it more flexible we'll just factor out the code in strategy classes. > * Make the default primary key metadata table named > "_geotools_pk_metadata". Hum... why the _? It is quite uncommon to have such named tables. I was looking into the Postgis system tables, all start with pg_, there is none starting with _. That makes it harder to conflict with something else, but looks odd imho. What about we use geotools_pk_metadata instead? And have a static method to override the default at the JDCBDataStoreFactory? I was thinking that for GeoServer gs_pk_metadata would make more sense. JDBCDataStoreFactory.setDefaultMetadataTableName(String name); Cheers Andrea -- Andrea Aime OpenGeo - http://opengeo.org Expert service straight from the developers. ------------------------------------------------------------------------------ Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
