QGIS » QGIS Application

Sorry to keep bothering but I still can't use Master to edit geometries with MSSQL.
I noticed some differences between the way 2.8.x and 2.14.x reads the geometry: https://goo.gl/r9sLq3

I'm not sure this is any help, but there you go

I'm just trying to edit a geometry, simple editions like to move. Sometimes create a geometry algo adds Z values.

It's happening in my SQLSERVER 2016 test server too.

Here is the data:
INSERT [dbo].[TUB_DISTRIBUICAO] ([OBJECTID], [GEOMETRY] ) VALUES (5, 0x0000000001158465C8A99E6122410DB59A90E7925F4131E2FE1DAC612241CFD91234E8925F4100000000000000000000000000000000 )
INSERT [dbo].[TUB_DISTRIBUICAO] ([OBJECTID], [GEOMETRY] ) VALUES (18913, 0x00000000011531E2FE1DAC612241CFD91234E8925F41D7C05B14E06122414EA0C180EA925F4100000000000000000000000000000000)

EPSG:29191
Using

Andre Jesus wrote:

I'm just trying to edit a geometry, simple editions like to move. Sometimes create a geometry algo adds Z values.

Unfortunately I can't reproduce. Moving and editing with the node tool doesn't produce Z geometries here.

This is not a isolated situation, all users in my network have the same problem. That's the reason we are stuck with 2.8.9.

If you wish I can set up a Teamviewer for you, so you can see what is going on, enable a debug, check the database... your call.

E-mail me.

The reporter has already left feedback and offered a way to have the issue checked, why tagging as feedback again?

Giovanni Manghi wrote:

The reporter has already left feedback and offered a way to have the issue checked, why tagging as feedback again?

We still need information to reproduce the problem.

Confirmed the same problem in 2.14.4 and 2.16.0

Installed 2.14.4, tested (error). uninstalled , cleared folders and windows registry.
Installed 2.16.0 , tested (error). uninstalled , cleared folders and windows registry.
Installed 2.14.4 x86, tested (error). uninstalled , cleared folders and windows registry.
Installed 2.8.9, tested (okey).

So, ever since the connection dialog changed for MSSQL, the problem with the geometry type started.

Problem persists: 2.16.1

This is how I manage to work around this problem:

I had to recreate all problematic geometries from WKT using the script below:

declare @txt varchar(max), @g geometry, @a int, @b int

set @a = (select min(oid) from TABLE)
  set @b = (select max(oid) from TABLE)

While (@a <= @b)
  begin
   set @txt = (select geometry.STAsText() from TABLE where oid = @a)
   set @g =  geometry::STGeomFromText(@txt, 0);
   update TABLE set geometry = @g where oid = @a
   set @a = (select min(oid) from TABLE where oid > @a)
  end

I'm working for a couple of hours and It all seems ok.
Does anyone knows why does It solved the problem?

I have a report from a MS SQL Server 2014 user that this issue in not confirmed, can anyone else give it a try?

Giovanni Manghi wrote:

I have a report from a MS SQL Server 2014 user that this issue in not confirmed, can anyone else give it a try?

Ever since I recreated all geometries in the database the problem never happened afterwards.

My theory is the geometries stored in the database had no SRID added to them, they all were SRID: 0.
When I recreated them I also validated invalid geometries and set the right SRID.

No problems so far.