Jody Garnett ha scritto: > I would also consider extending the format of updateSchema so we can supply > default expressions to the "new" columns.
I can propose another possibility as well. In JDBC data stores we use to put quite a bit of extra information as user data in each attribute: the native srid, or the native column type, and so on. We could do the same for updateSchema, establish a set of conventions that udpateSchema is supposed to follow to force a specific database native type or a specific default value. For example, what does it mean the attribute is a String? CHAR, VARCHAR, CLOB? What does it mean the attribute is a Double? Is it a DOUBLE, or a NUMBER(12,5)? Generally speaking there is quite a bit of native information that we don't capture in AttributeDescriptor. But we could put it in the associated user map. Cheers Andrea -- Andrea Aime OpenGeo - http://opengeo.org Expert service straight from the developers. ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
