[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [udig-devel] Re: [udig-users] ID of FID
|
andrea antonello wrote:
Not sure here. As a developer in these "standard" things I want to
rely on the "standard" tools of the application and not fork some
stuff and then maintain a fork.
It is more that we need to look at the code and see what we need to do;
there are some configuration options around
the handling of FeatureID.
I agree about that, but anyway for the shapefiles the fid is never
stable, since every time I edit and save, the fid column is refreshed
and the original fid table is lost.
When you update; add and delete it should be stable (perhaps only on
trunk?). Deleted rows may be filled in by subsequent adds as I recall.
I think you can set a Hint or configuration option to include keys as
readable attributes (up to you).
Again, I would not want to fork anything. Is this what you mean?
Lets figure out what we need - and then make it happen. The concept of
FeatureID is a poor one to delegate to a file format or database; it
probably should be defined as part of the data model IMHO. You can also
experiment and see if ShapefileDataStore will pick up an ID column as
the FeatureID; even if it does not you may enjoy the idea enough to
recommend it?
Jody
