Yup it is definitely a limitation that will need to be addressed. Although I don't think it is that outlandish for a first cut to just default column types to string with some preset length, and refine from there.
On 3/18/10 12:42 PM, Andrea Aime wrote: > Hi, > I was looking into the changes necessary to support > the creation of a new feature type via REST and > found some strong limitations in AttributeTypeInfo > that do not allow even a partial implementation. > > The idea was that we could POST a feature type description > to a datastore URL to create the new feature type. > Now, look at the feature type description format here: > http://docs.geoserver.org/stable/en/user/_downloads/featuretype_xml.txt > > Seeing anything missing in the attribute type descriptions? > Like... the data type, for example? :-p > > In order to support a minimal type creation imho > the attribute type description should contain: > - the data type (as a java class) > - the length restriction (important for any real world > usage of string types) > > Very much welcomed would be also the number of decimals > if we want to be able to create NUMBER(x,y) columns > in a database. > > Oh hum... looks like a trunk only change to me? > Well, in the meantime I'll play with a type creation GUI :-p > > Cheers > Andrea > -- Justin Deoliveira OpenGeo - http://opengeo.org Enterprise support for open source geospatial. ------------------------------------------------------------------------------ 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
