#2769: v.in.ogr not supporting OFTInteger64 field type
--------------------------------+-------------------------
Reporter: zarch | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 7.1.0
Component: Default | Version: svn-trunk
Keywords: v.in.ogr Integer64 | CPU: All
Platform: Linux |
--------------------------------+-------------------------
It seems that GRASS does not support vector columns with type int64, in
most of the cases this fields are just normal int32.
I've written a small patch that treat this field as normal integer (with a
warning). It works without problems on my test file... but I'm not sure
about the consequences if a real int64 is met.
What do you think? It is safe to move this changes to trunk?
#2769: v.in.ogr not supporting OFTInteger64 field type
---------------------+--------------------------------
Reporter: zarch | Owner: martinl
Type: defect | Status: assigned
Priority: normal | Milestone: 7.1.0
Component: Vector | Version: svn-trunk
Resolution: | Keywords: v.in.ogr Integer64
CPU: All | Platform: Linux
---------------------+--------------------------------
Comment (by martinl):
Replying to [ticket:2769 zarch]:
> It seems that GRASS does not support vector columns with type int64, in
most of the cases this fields are just normal int32.
>
> I've written a small patch that treat this field as normal integer (with
a warning). It works without problems on my test file... but I'm not sure
about the consequences if a real int64 is met.
support of int64 will depend on DB driver, eg. SQLite integers can hold
whatever you put into it: from a 1-byte char to an 8-byte long long (1).
PostgreSQL uses `int` and `bigint` (2), ...