On Mon, 01 Jun 2009 00:54:05 +0200, Nikos Alexandris <[email protected]> wrote:
> 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. > 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? I tried that but the problem remains. It seems as if there's problems importing such datetime columns. Thanks. -- Seb _______________________________________________ grass-user mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-user
