Opened 7 years ago

Closed 6 years ago

Last modified 6 years ago

#5904 closed defect (fixed)

CartoDB columns being create with case senstitivity

Reported by: pramsey Owned by: Even Rouault
Priority: normal Milestone: 2.0.0
Component: OGR_SF Version: svn-trunk
Severity: normal Keywords:
Cc:

Description

After loading a shape file, I found the following the in the columns:

{
   "total_rows" : 1,
   "fields" : {
      "CENTROID_Y" : {
         "type" : "number"
      },
      "the_geom" : {
         "type" : "geometry"
      },
      "B50K_TAG" : {
         "type" : "string"
      },
      "the_geom_webmercator" : {
         "type" : "geometry"
      },
      "PERIMETER" : {
         "type" : "number"
      },
      "B50K_BC_" : {
         "type" : "number"
      },
      "AREA" : {
         "type" : "number"
      },
      "cartodb_id" : {
         "type" : "number"
      },
      "CENTROID_X" : {
         "type" : "number"
      },
      "FCODE" : {
         "type" : "string"
      },
      "B50K_BC_ID" : {
         "type" : "number"
      }
   },
   "time" : 0.001,
   "rows" : [
      {
         "CENTROID_Y" : 1718935.4,
         "the_geom" : "010600...4D40",
         "B50K_TAG" : "114O/15",
         "the_geom_webmercator" : null,
         "PERIMETER" : 111715.55,
         "B50K_BC_" : 2,
         "AREA" : 780402750,
         "cartodb_id" : 1,
         "CENTROID_X" : 288014.38,
         "FCODE" : null,
         "B50K_BC_ID" : 1170
      }
   ]
}

I'm concerned that this will lead to tables being imported that are "hard to work with" since they'll all have columns that need to be quoted in every SQL statement. I'm pretty sure if I imported a shape file into PostGIS I wouldn't end up with all-caps column names, would I?

Change History (3)

comment:1 Changed 7 years ago by Even Rouault

Owner: changed from roualt to Even Rouault

The PostGIS driver actually "launders" (by default) table & field names to lower-case (and replace a few funny characters like single-quote, minus or sharp by underscore). The CartoDB one should likely do the same thing.

comment:2 Changed 6 years ago by Even Rouault

Milestone: 1.11.32.0
Resolution: fixed
Status: newclosed

trunk r28988 "CartoDB: launder layer and column names by default (#5904); Add also extensive testing with /vsimem/ simulation"

comment:3 Changed 6 years ago by Even Rouault

Milestone: 2.02.0.0

Milestone renamed

Note: See TracTickets for help on using tickets.