quote column names to avoid SQL reserved word collision

[hamish]

Hi,

moved here from GDAL bug # 2965 ​http://trac.osgeo.org/gdal/ticket/2965

v.in.ogr will not read GPX format as input because OGR's GPX driver creates a DB field called "time" for the timestamp. GRASS chokes on this because TIME is a SQL reserved word for some backends (DBF doesn't like it, SQLite is ok with it).

workaround: use the cnames= option to rename the TIME field.

suggestion by rouault: "There is no reason for the GPX driver not to use "time" as a field name. I think you should report it rather to the GRASS project. They should likely quote the field names (provided that it supports that). This is what the PG and MySQL driver in OGR do, so you can use any name, even if it is a SQL reserved keyword."

comments?

Hamish

[neteler]

For SQL reserved word collisions, see also #1755

[mlennert]

Replying to hamish:

suggestion by rouault: "There is no reason for the GPX driver not to use "time" as a field name. I think you should report it rather to the GRASS project. They should likely quote the field names (provided that it supports that). This is what the PG and MySQL driver in OGR do, so you can use any name, even if it is a SQL reserved keyword."

comments?

IMHO, quoting of field names is good practice in general, and so should be implemented in GRASS is possible.

Moritz

[martinl]

Milestone renamed

[neteler]

Ticket retargeted after milestone closed

[martinl]

All enhancement tickets should be assigned to 7.6 milestone.

[neteler]

Replying to neteler:

For SQL reserved word collisions, see also #1755

See also #3563

[martinl]

Ticket retargeted after milestone closed

[martinl]

Ticket retargeted after milestone closed