Skip to content

Should relationship mapping tables be present in gpkg_contents? #679

@nyalldawson

Description

@nyalldawson

This relates to discussion in OSGeo/gdal#9258 . Currently gdal does not write the mapping tables to gpkg_contents, and this seems to be compliant with the extensions specifications.

But is this intentional? By omitting them from gpkg_contents there's a risk that a client wont know to also check for tables in gpkgext_relations, and consequently refuse to open the mapping table (as current gdal versions fail to do).

Is the intentional that a client should scan for available tables in both gpkg_contents and gpkgext_relations?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions