Saul Farber wrote:
> Cool.  Glad you were able to get things testing jody.
>
> Re: arcsdepyramidtest -- yes, that's a problem.  I'll get that fixed as
> soon as I'm back in front of my dev station (thursday).
>
> Re: the filter tests failing and the use of calendar...I'll reply to
> that email seperately.
I got a second interesting problem (other than the Calendar one) ... 
this time from a customer.

The problem seems to relate to the introduction of versioning support. 
It shows up when the user is "splitting" a polygon in uDig (as a result 
they are creating a new feature and copying over all the arguments etc...).

[SDE error -170][Error desc=COLUMN IS NOT USER-MODIFIABLE.]

Guess which column produces this error? "OBJECTID" :-P Where ObjectId is 
its internal unique-id (the auto-increment sequence).

This produces an error in ArcSdeFeatureWriter.insertSeRow.

When the customer runs an older copy of ArcSDEDataStore (ie before 
versioning support was added) this problem does not occur. I am 
wondering if they screwed up their ArcSDE instance and have accidentally 
engaged the versioning support on one of their tables.  I will try and 
provide more information when I get back to ArcSDE work (on Friday?)

Jody





-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Geotools-devel mailing list
Geotools-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Reply via email to