Hi,
I wonder how it has been done in a new WFS plugin that can do transactions.
The transaction icon gets highlighted only if something has been modified, so I
think there must be some chance tracking system. And I don't believe really
that anybody makes a WFS-T client that sends the whole lay
Rahkonen Jukka wrote:
Hi,
> I wonder how it has been done in a new WFS plugin that can do transactions.
> The transaction icon gets highlighted only if something has been modified, so
> I think there must be some chance tracking system. And I don't believe really
> that anybody makes a WFS-T clie
Hi SS,
You missed the point. After loading the layer, with a simple boolean it
would always be set to true.
Larry
On Wed, Apr 1, 2009 at 5:34 PM, Sunburned Surveyor <
sunburned.surve...@gmail.com> wrote:
> Larry,
>
> I like your solution to this problem, but I wonder if it is necessary
> to
Larry wrote: "You missed the point. After loading the layer, with a
simple boolean it would always be set to true."
This must be due to the attributes being set once when the feature is
created from the data source when a layer is loaded. I see now that
your code accounts for this.
It is interes
I think the WFS code is probably just a case of having to implement Feature
modification detection at a higher level, since there was no low level
support for it. Modifications to BasicFeature (not AbstractFeatureClass
BTW) would not require a listener to detect changes. Therefor Feature
modifica
Larry Becker wrote:
Hi,
> I think the WFS code is probably just a case of having to implement Feature
> modification detection at a higher level, since there was no low level
> support for it. Modifications to BasicFeature (not AbstractFeatureClass
yes, I agree (although it was actually Ugo who
So I think we have come to an agreement then. :]
Larry: Do you want to try some modifications to the BasicFeature
class? If not, I can try to do it today or tomorrow.
SS
On Thu, Apr 2, 2009 at 8:27 AM, Andreas Schmitz wrote:
> Larry Becker wrote:
>
> Hi,
>
>> I think the WFS code is probably ju
I think I have found the cause of the "Change Styles fill patterns lockup
bug". I tried to duplicate the problem from Eclipse with the latest OJ code
and much to my surprise, it worked fine. In addition, the "missing" bitmap
fill patterns reappeared.
After a few minutes of checking I confirmed t
Andreas is right, for this to work for each "modified" Feature it must
be known if it was modified, inserted or deleted.
Also there's the case of conflict resolving.
If user "A" reads a Feature from a DB, modify it and then write it back
to the same DB, there's the possibility that in the meanti
SS,
The full mod to BasicFeature is attached. Why don't you go ahead with your
idea of testing it out with a "Select all modified Features" tool?
regards,
Larry
On Thu, Apr 2, 2009 at 10:44 AM, Sunburned Surveyor <
sunburned.surve...@gmail.com> wrote:
> So I think we have come to an agreement
Paolo,
You make some good points. I wasn't really trying to solve all database
update problems, but here is a try.
Assumption: The database PK is stored in an attribute. In this case
Features that show modified already have a PK so all is well. When new
Features are created, the PK will be
Larry: I'll squeeze in the code for a "Select All Modified Features
Tool" as soon as I get the chance.
Paolo: You post was a great summary of the challenges of implementing
true read/write support of features to a database in OpenJUMP. I think
it demonstrates why monitoring for this purpose needs
So.. I requested now to be a mentor for OSGeo using the google SofC
pages. I guess somebody at OSGeo will handle that?
... lets see what happens...
As I once previously pointed out, I am probably of in August so we need
to check later then how we submit the reports while I am traveling
stefan
Hei Larry,
great! and thank you - I modified the pom
(sorry for not having made a comment on the "track feature change"
thread since I haven't read all messages yet and I am just way to
unexperienced with such things, i.e.
feel not be able to make a "qualifying" contribution by what I have read
Hi,
I have seen two ways to generate unique IDs for new features. First one is
based on using integer as ID, and inserting new feature begins with query
"select max(ID) from table". New feature gets value max(ID)+1. Another, and
pretty safe way is to configure database table to take primary k
On Thu, Apr 2, 2009 at 4:15 PM, Rahkonen Jukka wrote:
> Hi,
>
> I have seen two ways to generate unique IDs for new features. First one is
> based on using integer as ID, and inserting new feature begins with query
> "select max(ID) from table". New feature gets value max(ID)+1. Another,
> and p
16 matches
Mail list logo
