#1834 closed enhancement (fixed)
KML Driver rev12157 - spaces in DB Table names generated from KML
Reported by: | darkblueB | Owned by: | Mateusz Łoskot |
---|---|---|---|
Priority: | low | Milestone: | 1.9.0 |
Component: | OGR_SF | Version: | unspecified |
Severity: | normal | Keywords: | sqlite |
Cc: | warmerdam |
Description
run the example soc_map_21.kml in ogr2ogr
ogr2ogr -f SQLite soc.sqlite soc_map_21.kml
notice that the output DB has 24 tables, and many of the table names have spaces in them, which confuses the dbms
Change History (3)
comment:1 by , 17 years ago
Cc: | added |
---|---|
Keywords: | sqlite added; kml removed |
Owner: | changed from | to
Priority: | normal → low |
Type: | defect → enhancement |
comment:2 by , 13 years ago
Milestone: | → 1.9.0 |
---|---|
Resolution: | → fixed |
Status: | new → closed |
comment:3 by , 3 years ago
Attachment has been deleted at request of someone whose private data was exposed into it.
Note:
See TracTickets
for help on using tickets.
Generally speaking OGR drivers are expected to return layer and field names as they are in the datasource. It is up to output drivers to offer name laundering options if they have restrictions. So I'm reclassifying this as an SQLLite bug report, with the idea that the sqlite driver ought to either quote field/table names so they work even if they have spaces, or it ought to offer a name laundering option.
I am deliberately leaving no milestone and reclassifying as an enhancement.