[GRASS-dev] v.in.ascii dependant on sqlite -> column limitation...

GRASS GIS GRASS GIS developer
1

Hi,

been modifying the buffer size on reading the ascii file and it could
eventually read all of the columns from my file (4020).
However, sqlite does not accepts that many of them... so v.in.ascii
does not complete the import.

any way to get v.in.ascii to enlarge its column capacity?

----------------
v.in.ascii input=9.csv output=rain_9 separator=comma
Scanning input for column types...
is_latlong east: 79.880000
Number of columns: 4020
DBMI-SQLite driver error:
Error in sqlite3_prepare():
too many columns on rain_9
---------------

--
Yann Chemin
Researcher@IWMI
Skype/FB: yann.chemin

2

Hi,

2013/5/6 Yann Chemin <yann.chemin@gmail.com>:

been modifying the buffer size on reading the ascii file and it could
eventually read all of the columns from my file (4020).
However, sqlite does not accepts that many of them... so v.in.ascii
does not complete the import.

any way to get v.in.ascii to enlarge its column capacity?

it's related to DB backend. For SQLite you would need to recompile
SQLite libs with custom SQLITE_MAX_COLUMN. In any case this number of
columns is not common.

Martin

[1] http://www.sqlite.org/limits.html