[udig-devel] feature bound issues

[Jesse Eichar]

Basically the idea is that a FID is supposed to be concrete and not  
change.  I know that it is not the case and I suggest using a  
Datastore that behaves well.  Postgis is pretty good if configured  
correctly and Shapefile is pretty reliable as well.  Although less so  
than Postgis.  Especially when a lot of feature deletes take place.


Also now that I think about it there can be an issue if a Issue is  
created before a commit.  At least until we make it to trunk.  Because  
the ID changes on a commit.

Jesse

Le 20-Feb-08 à 3:18 PM, andrea antonello a écrit :

> Hi all (I guess Jesse),
> I have a question about the features issues capability.
> How is an issue bound to a feature? I can't imagine anything that
> stays presistent, so I'm thinking how this works (more workflow, not
> code).
> Is the issue consistent until the layer name and FID changes? What
> happens when an issue doesn't find its feature any more?
>
> Thanks,
> Andrea
> _______________________________________________
> User-friendly Desktop Internet GIS (uDig)
> http://udig.refractions.net
> http://lists.refractions.net/mailman/listinfo/udig-devel