Bug report #4238

Geoserver WFS-T throws error when using QGIS Cut Spatial Objects tool

Added by Maria G Saavedra about 9 years ago. Updated almost 5 years ago.

Status:Closed
Priority:Low
Assignee:-
Category:Web Services clients/WFS
Affected QGIS version:master Regression?:No
Operating System:Windows 7 64 Bits Easy fix?:No
Pull Request or Patch supplied:No Resolution:not reproducable
Crashes QGIS or corrupts data:No Copied to github as #:14190

Description

Hi there

I use QGis with WFS Geoserver to edit spatial data in SQL Server 2008 R2, I load layers (tables) on QGis and edit. I 'm able to delete, create, and update geometry for polygons.
But when I use QGis Cut Spatial Objects tool, and save, I get an error:

java.lang.RuntimeException: Parsing failed for COLUMNNAME: java.lang.IllegalArgumentException: boolean indeterminate from ''
Parsin failed for IsOneWay: java.lang.IllegalArgumenntException: boolean indeterminate from ''
boolean indeterminaet from ''

Sometimes the column name change, and also the column type (boolean). Any ideas???

Windows 7 64 Bis
QGis 1.7.0
Geoserver 2.1.1
SQL Server 2008 R2

qgiserror.png (210 KB) Maria G Saavedra, 2011-08-30 08:46 AM

History

#1 Updated by Anita Graser almost 9 years ago

  • Subject changed from QGis and SQL Server (WFS Geoserver) to Geoserver WFS-T throws error when using QGIS Cut Spatial Objects tool

#2 Updated by Giovanni Manghi almost 9 years ago

  • Priority changed from Normal to Low

The error message comes from Geoserver, not QGIS, as it is clearly a JAVA error message.

In any case if you can't provide a server URL to allow further tests, it will be hard to debug this.

#3 Updated by Paolo Cavallini almost 9 years ago

  • Category set to Web Services clients/WFS

#4 Updated by Giovanni Manghi almost 9 years ago

  • Target version set to Version 1.7.4

#5 Updated by Paolo Cavallini over 8 years ago

  • Affected QGIS version set to master
  • Crashes QGIS or corrupts data set to No
  • Target version changed from Version 1.7.4 to Version 1.8.0

#6 Updated by Paolo Cavallini about 8 years ago

  • Target version changed from Version 1.8.0 to Version 2.0.0

#7 Updated by Jürgen Fischer over 6 years ago

  • Target version changed from Version 2.0.0 to Future Release - Lower Priority

#8 Updated by Médéric RIBREUX almost 5 years ago

  • Status changed from Open to Feedback

Hello, bug triage...

do you still have this bug with a recent version of QGIS (2.12.1 or master) and a recent version of Geoserver ?

Trying to reproduce this bug is very hard for people without the same production environment you have. So if the bug is still present, we need more details and tests about it to determine if it is a QGIS or a Geoserver or an MS-SQL server problem (try with another client than QGIS for example).

#9 Updated by Giovanni Manghi almost 5 years ago

  • Status changed from Feedback to Closed
  • Resolution set to not reproducable

closing for lack of feedback.

Also available in: Atom PDF