id summary reporter owner description type status priority milestone component version severity resolution keywords cc 5904 CartoDB columns being create with case senstitivity pramsey Even Rouault "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?" defect closed normal 2.0.0 OGR_SF svn-trunk normal fixed