Bug report #16038
Qgis problem with PostGIS trigger
| Status: | Closed | ||
|---|---|---|---|
| Priority: | Normal | ||
| Assignee: | - | ||
| Category: | Data Provider/PostGIS | ||
| Affected QGIS version: | 2.18.2 | Regression?: | No |
| Operating System: | Easy fix?: | No | |
| Pull Request or Patch supplied: | No | Resolution: | end of life |
| Crashes QGIS or corrupts data: | No | Copied to github as #: | 23953 |
Description
I have a PostGIS table with date modified column trigger and whenever some features are added or edited in table, date modified column changes automatically. In QGIS layer properties for same table, for date modified column, date/time value is used (layer properties/fields/edit widget) and saved as default style in database so that whenever some features are added it is visible in the feature attribute form easily.
Now, when I start editing mode first and open attribute table for the layer, one of the row of date modified column automatically changes to current time even without editing or modifying anything in the layer and QGIS prompts to save the table even if nothing is modified in the layer (only the layer is in editing mode and attribute table is opened)
It seems that QGIS edit widget contradicts with working of postgis trigger function or the other way around for some reason.
trigger_function.txt 
- trigger function used that causes problem with QGIS edit field widget
(582 Bytes)
History
#1
Updated by Sujan Dahal over 7 years ago
- Assignee deleted (
Jürgen Fischer)
#2
Updated by Giovanni Manghi almost 7 years ago
- Easy fix? set to No
- Regression? set to No
#3
Updated by Giovanni Manghi about 5 years ago
- Resolution set to end of life
- Status changed from Open to Closed
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.