Repository navigation
Feat: Register non-spatial GeoPackage tables in gpkg_contents - #600
Open
adrien-berchet with Copilot wants to merge 4 commits into
Open
adrien-berchet with Copilot wants to merge 4 commits into
adrien-berchet with Copilot wants to merge 4 commits into
Conversation
Copilot
AI
changed the title
[WIP] Add support for non-spatial tables in Geopackages
Feat: Register non-spatial GeoPackage tables in Apr 13, 2026
gpkg_contents
adrien-berchet
force-pushed
the
copilot/add-non-spatial-tables-support
branch
from
July 7, 2026 20:33
95e63ed to
fc3323c
Compare
Agent-Logs-Url: https://github.com/geoalchemy/geoalchemy2/sessions/f5b8a299-1de5-4fce-9881-d3a8fb9b51ad Co-authored-by: adrien-berchet <11536226+adrien-berchet@users.noreply.github.com>
Agent-Logs-Url: https://github.com/geoalchemy/geoalchemy2/sessions/f5b8a299-1de5-4fce-9881-d3a8fb9b51ad Co-authored-by: adrien-berchet <11536226+adrien-berchet@users.noreply.github.com>
Non-spatial tables created with the GeoPackage dialect are now registered in gpkg_contents with data_type='attributes' and srs_id=NULL (GeoPackage spec, Requirement 118). Only tables with a single INTEGER primary key acting as a rowid alias are registered (Requirement 119), so tables like alembic_version, WITHOUT ROWID tables and temporary tables are left unregistered. The registration is skipped when the GeoPackage base tables do not exist yet, and works in Alembic offline mode. Alembic table renames (including batch mode) keep the gpkg_contents row in sync.
adrien-berchet
force-pushed
the
copilot/add-non-spatial-tables-support
branch
from
November 4, 2026 19:56
fc3323c to
89c4b73
Compare
adrien-berchet
marked this pull request as ready for review
November 4, 2026 22:10
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
GeoPackage consumers expect all tables (including non-spatial) to be discoverable via
gpkg_contents; currently only spatial tables are registered. This PR adds spec-aligned handling for non-spatial tables so they are created asattributesentries and removed cleanly on drop.Dialect behavior updates
after_createnow inserts agpkg_contentsrow for tables without geometry columns:data_type = 'attributes'srs_id = 0before_dropnow removes the correspondinggpkg_contentsrow for non-spatial tables.Focused regression coverage
Checklist
This pull request is:
mainbranch and pass with the provided fix.