We do have getInfo() which we can add to. I would prefer to use an open end Map/Key combo until we settle down on what is needed (much like how we treat Parameter.metadata right now.
Jody On 22/04/2010, at 11:27 PM, Andrea Aime wrote: > Andrea Aime ha scritto: >> This is similar to Jody's point. However, we don't have anything like >> that for createSchema and updateSchema either. >> Such a capabilities API should probably also provide some hints on how >> type and attribute names are transformed by createSchema to make it >> possible to create a data transfer tool (which today is hard to >> implement as Oracle and SDE tend to mangle the provided names). > > Other things that would be interesting to have in a capabilities API: > - list of actual types supported by the store (does it do Timestamps? > Time? Or just Date? What about byte[]?) > - can it get any hint to better specify the underlying storage type? > Something like JDBC_NATIVE_TYPE in the attribute descriptor to > actually specify that you want a CHAR(20) and not a VARCHAR(20) > or that you want a timestamp with time zone? > > 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 ------------------------------------------------------------------------------ _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
