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 ne
Andrea Aime ha scritto:
> Oh hum... looks like a trunk only change to me?
> Well, in the meantime I'll play with a type creation GUI :-p
Humm... tried to actually use the rest config instead but
I'm getting stuck.
So, I've added the necessary fields to AttributeTypeInfo
and I was expecting to see
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 ne
Right, this is done intentionally because we assume that an empty
getAttributes() means derive them from the underlying feature type. The
reason the persister uses getAttributes() and not attributes() is
because if the attributes get stored on disk it then assumes the user
has performed a manua
