The Ok button for the form dialog is disabled for NOT NULL Postgres columns

[qgib]

Author Name: Tudor Bărăscu (@tudorbarascu) Original Redmine Issue: 19671 Affected QGIS version: 3.5(master) Redmine category:forms

---

Some Postgres NOT NULL columns are filled automatically database side but the QGIS Dialog enforces filling of values. I found no way to disable this.

To recreate:

CREATE TABLE testtable (id serial PRIMARY KEY, status integer NOT NULL, geom geometry(Point, 4326));

• Add the table to a project.
• Imagine there's a trigger/function that fills the status column automatically.
• Try and add a feature without filling the status column
• Problem: Cannot Save the dialog

---

• problem.jpg (Tudor Bărăscu)
• problem1.jpg (Tudor Bărăscu)

---

Related issue(s): #28650 (relates) Redmine related issue(s): 20831

---

[qgib]

Author Name: Alessandro Pasotti (@elpaso)

---

How do you think QGIS would know if a NOT NULL column is filled by a trigger?

Do you have any solution in mind?

[qgib]

Author Name: Alessandro Pasotti (@elpaso)

---

• status_id was changed from Open to Feedback

[qgib]

Author Name: Tudor Bărăscu (@tudorbarascu)

---

From my perspective, it should all function like this:

• When QGIS detects the NOT NULL column, the QGIS side NOT NULL contraint should be enabled automagically
• However, the user should have the option to disable it The user should be able to uncheck the Not Null checkbox in the constraints part

Sounds good?

Thank you for taking a look Alessandro!

---

• 13187 was configured as problem1.jpg

---

• problem1.jpg (Tudor Bărăscu)

[qgib]

Author Name: Alessandro Pasotti (@elpaso)

---

That sounds reasonable to me, perhaps also issue a warning when the user unticks the checkbox: "The fields is marked NOT NULL but you are overriding this check, if you do not fill this field and there is nothing to set its value the operation will probably be rejected by the backend".

Changing to feature request (ok, I know it's debatable :)

---

• tracker_id was changed from 1 to 2

[qgib]

Author Name: Tudor Bărăscu (@tudorbarascu)

---

• status_id was changed from Feedback to Open

[qgib]

Author Name: Nyall Dawson (@nyalldawson)

---

• assigned_to_id was configured as Nyall Dawson

[qgib]

Author Name: Nyall Dawson (@nyalldawson)

---

Does this relate to #27895 ?

---

• status_id was changed from Open to Feedback
• assigned_to_id removed Nyall Dawson

[qgib]

Author Name: Tudor Bărăscu (@tudorbarascu)

---

@Nyall Yes! IMHO It's ok that the forms get the constraints automatically but the settings of the constraints should override this.

[qgib]

Author Name: Tudor Bărăscu (@tudorbarascu)

---

A workaround would be to simply fill those specific columns with a default value, -1 let's say and it will let you pass while the database logic will change it to what's supposed to be.

---

• status_id was changed from Feedback to Open

[qgib]

Author Name: Hugo Mercier (@mhugo)

---

• relates was configured as #28650

[qgib]

Author Name: Hugo Mercier (@mhugo)

---

Tudor, about your proposed workaround, I observed this is not even possible when the primary key has the default widget "Range". It seems the Range widget does not take the default value into account. However changing the widget type to "Text editor" allows to use a default value (and postgres is ok to receive a text for an integer)

Related issue #28650

[qgib]

Author Name: Hugo Mercier (@mhugo)

---

• assigned_to_id was configured as Hugo Mercier

[qgib]

Author Name: Hugo Mercier (@mhugo)

---

• assigned_to_id removed Hugo Mercier

[qgib]

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

---

• tracker_id was changed from 2 to 1
• version was configured as 3.5(master)
• crashes_corrupts_data was configured as 0
• regression was configured as 1

[Pedro-Murteira]

Still valid on QGIS 3.22.3.