Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Attribute table] Range widget arrow value is set to -2 147 483 645 #29019

Open
qgib opened this issue Feb 8, 2019 · 7 comments
Open

[Attribute table] Range widget arrow value is set to -2 147 483 645 #29019

qgib opened this issue Feb 8, 2019 · 7 comments
Labels
Attribute Table Bug Either a bug report, or a bug fix. Let's hope for the latter! Regression Something which used to work, but doesn't anymore

Comments

@qgib
Copy link
Contributor

qgib commented Feb 8, 2019

Author Name: Harrissou Santanna (@DelazJ)
Original Redmine Issue: 21201
Affected QGIS version: 3.5(master)
Redmine category:attribute_table


Trying to change value of a postgres integer field in attribute table, I clicked on the up arrow, expecting to get 0 (from null) and it returns -2 147 483 645
Clicking the up or down arrow to change the value has no effect.
The only workaround is to manually type in a value (let's say 0) and then you can change the value using the arrows.

Hugo, just pinging you as I notice you made some recent changes to this widget

@qgib
Copy link
Contributor Author

qgib commented Feb 8, 2019

Author Name: Giovanni Manghi (@gioman)


  • priority_id was changed from Normal to High

@qgib
Copy link
Contributor Author

qgib commented Feb 11, 2019

Author Name: Hugo Mercier (@mhugo)


Trying to change value of a postgres integer field in attribute table, I clicked on the up arrow, expecting to get 0 (from null) and it returns -2 147 483 645

Yes it returns the minimum value ... the 'null' value must be an actual value. If you expect 0, you expect null to be -1 ? Is it better than -2 147 483 648

Clicking the up or down arrow to change the value has no effect.

I can't reproduce on master ...

@qgib
Copy link
Contributor Author

qgib commented Feb 13, 2019

Author Name: Alexander Bruy (@alexbruy)


  • status_id was changed from Open to Feedback

@qgib
Copy link
Contributor Author

qgib commented Feb 14, 2019

Author Name: Harrissou Santanna (@DelazJ)


If you expect 0, you expect null to be -1 ? Is it better than -2 147 483 648

Good point. actually I haven't thought so far. But I'm pretty sure that nobody will be in need for -2 147 483 648 when hitting the arrow. People will most of the times go from 0 up or down.

I can't reproduce on master ...

Me neither. Actually I can reproduce none of the two issues I describe, using either 0d178aa or dabd649. Hitting the up arrow brings me to 0 and I can't get -1 (so no luck for -2 147 483 648 :D) when hitting the down arrow: values are set positive by default. I am still using the same PG layers as in the initial report with no changes made to fields meanwhile. Were your changes reverted?

@qgib
Copy link
Contributor Author

qgib commented Feb 18, 2019

Author Name: Giovanni Manghi (@gioman)


  • status_id was changed from Feedback to Open

@qgib qgib added Bug Either a bug report, or a bug fix. Let's hope for the latter! High Priority Attribute Table Regression Something which used to work, but doesn't anymore labels May 25, 2019
@gioman
Copy link
Contributor

gioman commented Aug 4, 2020

Trying to change value of a postgres integer field in attribute table, I clicked on the up arrow, expecting to get 0 (from null) and it returns -2 147 483 645

trying the latest master and the above is still true.

@Pedro-Murteira
Copy link

Pedro-Murteira commented Feb 15, 2022

This is still the case on QGIS 3.22.3. (Windows 10)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Attribute Table Bug Either a bug report, or a bug fix. Let's hope for the latter! Regression Something which used to work, but doesn't anymore
Projects
None yet
Development

No branches or pull requests

3 participants