Opened 7 years ago

Closed 7 years ago

Last modified 7 years ago

#6916 closed defect (fixed)

GPKG: issue with ArcMap databases with inconsistance case for table name

Reported by: Even Rouault Owned by: warmerdam
Priority: normal Milestone: 2.1.4
Component: OGR_SF Version: unspecified
Severity: normal Keywords: gpkg
Cc:

Description

ArcMap generates databases where table_name in gpkg_contents and gpkg_geometry_columns is equal, but the case is not the same as the name in sqlite_master. This cause issues as OGR use strict equality for some comparisons/joins

Change History (7)

comment:1 by Even Rouault, 7 years ago

Resolution: → fixed
Status: assigned → closed

In 38918:

GPKG: make driver robust to difference of cases between table_name in gpkg_contents/gpkg_geometry_columns and name in sqlite_master (fixes #6916)

comment:2 by Even Rouault, 7 years ago

In 38919:

GPKG: make driver robust to difference of cases between table_name in gpkg_contents/gpkg_geometry_columns and name in sqlite_master (fixes #6916)

comment:3 by Even Rouault, 7 years ago

In 38920:

GPKG: make driver robust to difference of cases between table_name in gpkg_contents/gpkg_geometry_columns and name in sqlite_master (fixes #6916)

comment:4 by Even Rouault, 7 years ago

In 38921:

GPKG: more robustness regarding table/column name case (fixes #6916)

comment:5 by Even Rouault, 7 years ago

In 38922:

GPKG: more robustness regarding table/column name case (fixes #6916)

comment:6 by Even Rouault, 7 years ago

In 38923:

GPKG: more robustness regarding table/column name case (fixes #6916)

comment:7 by Even Rouault, 7 years ago

In 38924:

Test fix (refs #6916)

Note: See TracTickets for help on using tickets.