Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

replace <geopackage>$con with <geopackage>$env$con #11

Merged
merged 4 commits into from
Jun 18, 2023
Merged

Conversation

brownag
Copy link
Owner

@brownag brownag commented Jun 18, 2023

In this PR each geopackage stores the connection object (and in the future possibly other things) in an internal environment <geopackage>$env

  • allows for in-place gpkg_connect() with no assignment into user/parent env (replacement for attempt in Updates to gpkg_connect() #9), as the environment can be updated with the result object still pointing to same reference

 - allows for in-place gpkg_connect() with no assignment into user/parent env
@brownag brownag linked an issue Jun 18, 2023 that may be closed by this pull request
@brownag brownag linked an issue Jun 18, 2023 that may be closed by this pull request
@brownag brownag merged commit 99906b1 into main Jun 18, 2023
8 checks passed
@brownag brownag deleted the gpkg-connect-2 branch February 13, 2024 18:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

consider use of R6 for geopackage in-place modification for gpkg_connect()
1 participant