Opened 9 years ago
Closed 9 years ago
#2769 closed defect (fixed)
v.in.ogr not supporting OFTInteger64 field type
Reported by: | zarch | Owned by: | martinl |
---|---|---|---|
Priority: | normal | Milestone: | 7.0.4 |
Component: | Vector | Version: | svn-trunk |
Keywords: | v.in.ogr Integer64 | Cc: | grass-dev@… |
CPU: | All | Platform: | Linux |
Description
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?
Attachments (1)
Change History (8)
by , 9 years ago
Attachment: | v.in.ogr_OFTInteger64.diff added |
---|
comment:1 by , 9 years ago
Cc: | added |
---|---|
Component: | Default → Vector |
Owner: | changed from | to
Status: | new → assigned |
comment:2 by , 9 years ago
Replying to 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), ...
(1) http://www.sqlite.org/datatype3.html (2) http://www.postgresql.org/docs/9.4/static/datatype-numeric.html
comment:5 by , 9 years ago
Replying to martinl:
Can we close the ticket (with milestone 7.1)?
yes, it works for me. Thanks
Pietro
comment:6 by , 9 years ago
Milestone: | 7.1.0 → 7.0.4 |
---|
Backported to relbr70 in r67742. Closing.
comment:7 by , 9 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Patch to treat OFTInteger64 field as OFTInteger64