Spatialite, PostGIS layers with 8-byte primary keys don't display in Identify tool

[qgib]

Author Name: Brian Freed (@bfreed)
Original Redmine Issue: 8435
Affected QGIS version: 1.8.0

---

Looks like there was an old issue with other layer providers: Issues #15546, #11980, #10121, etc. for PostGIS, MSSQL

SQLite only has one INTEGER type for column declaration. It determines whether to store as 4, 6, or 8-byte values.
I have a view in PostGIS with BIGINT primary keys. I'm exporting to a Spatialite database table; since all keys are larger than the 4-byte limit, I assume SQLite is using 8-byte storage.

When I load the PostGIS view in QGIS, the rows show correctly in the Attribute Table.
When I load the Spatialite table in QGIS, the rows display a negative number for the primary key column.

In both cases, the Identify Features tool fails to do anything.
With Spatialite it fails silently.
With PostGIS I get a Log Message like 'feature -148753075 not found' (the actual primary key is a very large positive number)

After some digging, I found a workaround I'll try next:
http://linfiniti.com/2011/11/adding-a-counter-to-postgresql-query-results/

Since there's a workaround, I'm picking 'low priority'.
If it's an inherent Qt limitation, maybe QGIS could raise a prompt with advice, to avoid users re-searching a known problem.

[qgib]

Author Name: Giovanni Manghi (@gioman)

---

have you tested qgis master?

---

• status_id was changed from Open to Feedback

[qgib]

Author Name: Jürgen Fischer (@jef-n)

---

closing for the lack of feedback.

---

• resolution was changed from to worksforme
• status_id was changed from Feedback to Closed