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

"money" type (postgresql) interpreted as string #25529

Closed
qgib opened this issue Dec 5, 2017 · 9 comments · Fixed by #57513
Closed

"money" type (postgresql) interpreted as string #25529

qgib opened this issue Dec 5, 2017 · 9 comments · Fixed by #57513
Assignees
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Expressions Related to the QGIS expression engine or specific expression functions PostGIS data provider

Comments

@qgib
Copy link
Contributor

qgib commented Dec 5, 2017

Author Name: Loïc BARTOLETTI (@lbartoletti)
Original Redmine Issue: 17632
Affected QGIS version: 3.5(master)
Redmine category:field_calculator


In composer and virtual field, I have this error.

Try to add numeric fields and return NULL (decimal field for virtual field) or a string concatenation into composer.


@qgib
Copy link
Contributor Author

qgib commented Dec 5, 2017

Author Name: Harrissou Santanna (@DelazJ)


Could it have to do with the € suffix in the fields ?

@qgib
Copy link
Contributor Author

qgib commented Dec 5, 2017

Author Name: Loïc BARTOLETTI (@lbartoletti)


Sorry it's Money type from postgis and not a numeric field.

@qgib
Copy link
Contributor Author

qgib commented Dec 5, 2017

Author Name: Giovanni Manghi (@gioman)


  • subject was changed from Addition of numeric type (postgis) interpreted as string to Addition of "money" type (postgis) interpreted as string

@qgib
Copy link
Contributor Author

qgib commented Dec 5, 2017

Author Name: Giovanni Manghi (@gioman)


  • subject was changed from Addition of "money" type (postgis) interpreted as string to "money" type (postgresql) interpreted as string

@qgib
Copy link
Contributor Author

qgib commented Jan 20, 2019

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


Please test with QGIS 3.4 - QGIS 2.18 reached it's end of life.


  • status_id was changed from Open to Feedback

@qgib
Copy link
Contributor Author

qgib commented Jan 28, 2019

Author Name: Loïc BARTOLETTI (@lbartoletti)


Confirmed in master


  • version was changed from 2.18.14 to 3.5(master)
  • 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! Expressions Related to the QGIS expression engine or specific expression functions labels May 25, 2019
@Pedro-Murteira
Copy link

Still valid on QGIS 3.16.15 and 3.22.2.

@alexbruy alexbruy added PostGIS data provider Expressions Related to the QGIS expression engine or specific expression functions and removed Expressions Related to the QGIS expression engine or specific expression functions labels Nov 12, 2023
@strk
Copy link
Contributor

strk commented May 22, 2024

Use of "money" type is discouraged: https://wiki.postgresql.org/wiki/Don't_Do_This#Don.27t_use_money

That said, what is the desired behavior ? Should it be treated as numeric ?

@strk
Copy link
Contributor

strk commented May 22, 2024

PR GH-57513 threats those money values as numbers, @Pedro-Murteira @lbartoletti would you mind giving it a try ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Expressions Related to the QGIS expression engine or specific expression functions PostGIS data provider
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants