Seb:
> I tried importing a PostgreSQL table (a view) using
v.in.ogr. However the module failed
...
> The warning about the sex column is harmless since it is just a custom
> type and the 255 limit is fine here. The parsing error with time column
> seems to have prevented the vector from building properly though. The
> same error occurs when doing it with v.in.db. The view and the
> underlying tables show no problems in Postgresql.
Nikos:
Not sure if this is a conflict with SQL commands, but you could try to
_feed_ new names for your columns by using the "cname=" paramater of
"v.in.ogr" and see what happens?
"time" is a reserved SQL keyword, and column names are not someway quoted,
so it conflicts.
see: https://trac.osgeo.org/grass/ticket/578
Hamish