QGIS » QGIS Application

Sorry for the unclear description.
I just check the real case scenario and the postgresql field (containing negative and positive values) is of type "bigint"

nb : there's a (unique, btree) index on the field that causes the issue
I don't know if it has any relation with the current issue. I didn't try to reproduce the issue when removing the index. I'll do it asap.

c m wrote:

nb : there's a (unique, btree) index on the field that causes the issue
I don't know if it has any relation with the current issue. I didn't try to reproduce the issue when removing the index. I'll do it asap.

Hi thanks for the report. Could you add a dump of the problematic table? thanks.

Here's a script that you could use to reproduce the issue :

DROP TABLE IF EXISTS public.to_delete cascade;

CREATE TABLE public.to_delete
(
  id integer NOT NULL,
  the_geom geometry,
  CONSTRAINT id_idx_primkey PRIMARY KEY (id),
  CONSTRAINT id_idx_unique UNIQUE (id),
  CONSTRAINT enforce_dims_the_geom CHECK (st_ndims(the_geom) = 2),
  CONSTRAINT enforce_geotype_the_geom CHECK (geometrytype(the_geom) = 'LINESTRING'::text OR the_geom IS NULL),
  CONSTRAINT enforce_srid_the_geom CHECK (st_srid(the_geom) = 4326)  
);

SELECT Populate_Geometry_Columns('public.to_delete'::regclass);

insert into public.to_delete values (1, ST_GeomFromText('LINESTRING(-71.160281 42.258729,-71.160837 42.259113,-71.161144 42.25932)', 4326));
insert into public.to_delete values (-1, ST_GeomFromText('LINESTRING(-71.161144 42.25932,-71.160837 42.259113,-71.160281 42.258729)', 4326));

Then connect a QGIS v2.x to view this table
open the table's view and you'll see an "ERROR" value for field "id" in line 2

replicate is easy: import with osm2pgsql a osm dataset, the "osm_id" field (int8) will show this wrong behavior.