When I create a field with an integer (64-bit) and edit the value to 9223372036854775806, then enter it, the value changes to 9223372036854776000. It seems to behave like a double.
I found out that this issue occurs because the value is stored as a double when exporting with PostGIS.
Steps to reproduce the issue
create a field with an integer (64-bit) and edit the value to 9223372036854775806, then save it
Versions
QGIS 버전
3.34.3-Prizren
QGIS 코드 리버전
47373234ac
Qt version
5.15.3
Python version
3.9.18
GDAL/OGR version
3.8.3
PROJ version
9.3.1
EPSG Registry database version
v10.098 (2023-11-24)
GEOS version
3.12.1-CAPI-1.18.1
SQLite version
3.41.1
PDAL version
2.6.0
PostgreSQL client version
15.2
SpatiaLite version
5.1.0
QWT version
6.1.6
QScintilla2 version
2.13.4
OS version
Windows 10 Version 2009
What is the bug or the crash?
When I create a field with an integer (64-bit) and edit the value to 9223372036854775806, then enter it, the value changes to 9223372036854776000. It seems to behave like a double. I found out that this issue occurs because the value is stored as a double when exporting with PostGIS.
Steps to reproduce the issue
create a field with an integer (64-bit) and edit the value to 9223372036854775806, then save it
Versions
QGIS 버전 3.34.3-Prizren QGIS 코드 리버전 47373234ac Qt version 5.15.3 Python version 3.9.18 GDAL/OGR version 3.8.3 PROJ version 9.3.1 EPSG Registry database version v10.098 (2023-11-24) GEOS version 3.12.1-CAPI-1.18.1 SQLite version 3.41.1 PDAL version 2.6.0 PostgreSQL client version 15.2 SpatiaLite version 5.1.0 QWT version 6.1.6 QScintilla2 version 2.13.4 OS version Windows 10 Version 2009
Active Python plugins tmsforkorea 3.0.5 db_manager 0.1.20 grassprovider 2.12.99 MetaSearch 0.3.6 processing 2.12.99
Supported QGIS version
New profile
Additional context
When I add a new attribute as int64, it seems to work correctly, but if I add another one, before attribute changes to double. so confuse.