New PostGIS/SpatiaLite table - Inconsistent behavior of primary keys

[qgib]

Author Name: Reinhard Reiterer (Reinhard Reiterer)
Original Redmine Issue: 15079
Affected QGIS version: 2.14.3
Redmine category:db_manager

---

Please create a new PostGIS and a new SpatiaLite table in the 'DB Manager'. In both cases select 'integer' (data type) for the primary key. When adding new features the PostGIS pk has to be set manually, the SpatiaLite pk is created automatically.

See also:

#23014 Create table dialog (SpatiaLite) misses data type 'Serial'
#23019 Create table dialog lists useless data types for SpatiaLite

---

• postgis_spatialite_pk.mp4 (Reinhard Reiterer)
• postgis_dummy.png (Reinhard Reiterer)
• spatialite_dummy.png (Reinhard Reiterer)

---

Related issue(s): #23014 (relates)
Redmine related issue(s): 15071

---

[qgib]

Author Name: Reinhard Reiterer (Reinhard Reiterer)

---

• 10044 was configured as postgis_spatialite_pk.mp4

---

• postgis_spatialite_pk.mp4 (Reinhard Reiterer) - screencast

[qgib]

Author Name: Reinhard Reiterer (Reinhard Reiterer)

---

Perhaps tooltips could help to improve the 'Create Table' dialogs.

I did some tests and for new SpatiaLite tables 'bigint' and 'smallint' do not support auto increment primary key fields. But I suppose this is the expected behavior.

---

• 10060 was configured as spatialite_dummy.png
• 10059 was configured as postgis_dummy.png

---

• spatialite_dummy.png (Reinhard Reiterer)
• postgis_dummy.png (Reinhard Reiterer)

[qgib]

Author Name: Giovanni Manghi (@gioman)

---

• regression was configured as 0
• easy_fix was configured as 0

[qgib]

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

---

• relates was configured as Create table dialog (SpatiaLite) misses data type 'Serial' #23014

[qgib]

Author Name: Giovanni Manghi (@gioman)

---

End of life notice: QGIS 2.18 LTR

Source:
http://blog.qgis.org/2019/03/09/end-of-life-notice-qgis-2-18-ltr/

QGIS 3.4 has recently become our new Long Term Release (LTR) version. This is a major step in our history – a long term release version based on the massive updates, library upgrades and improvements that we carried out in the course of the 2.x to 3x upgrade cycle.

We strongly encourage all users who are currently using QGIS 2.18 LTR as their preferred QGIS release to migrate to QGIS 3.4. This new LTR version will receive regular bugfixes for at least one year. It also includes hundreds of new functions, usability improvements, bugfixes, and other goodies. See the relevant changelogs for a good sampling of all the new features that have gone into version 3.4

Most plugins have been either migrated or incorporated into the core QGIS code base.

We strongly discourage the continued use of QGIS 2.18 LTR as it is now officially unsupported, which means we’ll not provide any bug fix releases for it.

You should also note that we intend to close all bug tickets referring to the now obsolete LTR version. Original reporters will receive a notification of the ticket closure and are encouraged to check whether the issue persists in the new LTR, in which case they should reopen the ticket.

If you would like to better understand the QGIS release roadmap, check out our roadmap page! It outlines the schedule for upcoming releases and will help you plan your deployment of QGIS into an operational environment.

The development of QGIS 3.4 LTR has been made possible by the work of hundreds of volunteers, by the investments of companies, professionals, and administrations, and by continuous donations and financial support from many of you. We sincerely thank you all and encourage you to collaborate and support the project even more, for the long term improvement and sustainability of the QGIS project.

---

• resolution was changed from to end of life
• status_id was changed from Open to Closed