[GRASS-dev] [GRASS GIS] #2184: MySQL Error during 'v.in.ogr' in GRASS 7 SVN (2014-01-31)
GRASS GIS
trac at osgeo.org
Sat Feb 15 14:28:51 PST 2014
#2184: MySQL Error during 'v.in.ogr' in GRASS 7 SVN (2014-01-31)
-------------------------+--------------------------------------------------
Reporter: justinzane | Owner: grass-dev@…
Type: defect | Status: closed
Priority: normal | Milestone: 7.0.0
Component: Vector | Version: svn-trunk
Resolution: invalid | Keywords: MySQL, OGR, import
Platform: Linux | Cpu: x86-64
-------------------------+--------------------------------------------------
Changes (by neteler):
* status: new => closed
* resolution: => invalid
Comment:
According to
* http://dev.mysql.com/doc/refman/5.7/en/reserved-words.html
* http://dev.mysql.com/doc/refman/5.7/en/identifiers.html
* http://stackoverflow.com/questions/12658763/why-did-i-have-to-use-
backticks-around-the-table-name-in-my-mysql-query
backticks are required if the identifier is a reserved word, contains
white space, etc.
The word "NATURAL" is a reserved word in MySQL (see Table 9.2 in the first
link).
To solve this conflict for you, you can use the "cnames" parameter of
v.in.ogr to
change the column names during import. The GRASS DB drivers should not try
to
automatically launder names.
To give more help in the manual, I have added some remarks in r59058
(backported in
r59059 and r59060).
Closing.
--
Ticket URL: <http://trac.osgeo.org/grass/ticket/2184#comment:2>
GRASS GIS <http://grass.osgeo.org>
More information about the grass-dev
mailing list