That is, I guess, because sqlite 'uses dynamic typing. It does not enforce data type constraints. Data of any type can (usually) be inserted into any column. '?
On October 6, 2021 5:25:47 PM Rich Shepard <rshep...@appl-ecosys.com> wrote:
I learned something surprising this morning using a combination of the GUI management window's map 'display table attributes' and db.execute. The two adjacent bathymetric point files imported with a Z-int column with type double precision for the integer depths. However, the depth values displayed are in double precision format (ending in .00). I added a new column, depth_int (type int), and copied (using SQL's 'alter table') the Z-int double precision values to the depth_int column, then deleted the Z-int column. The GUI's attribute table management dialog confirmed that the depth_int is of type integer. After re-displaying these maps the depth values are still double precision while the column data type is integer. Oh well. Rich _______________________________________________ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user
_______________________________________________ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user
