Allow spatialite-enabled database connections.#8
Open
richardellison wants to merge 1 commit into
Open
Conversation
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
1 participant
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.
I have been working with some Spatialite databases recently and realised that many of the same spatial functions, including the ones used in this package, also apply to Spatialite-enabled databases so the same code can support both PostgreSQL/PostGIS and Spatialite. This PR adds the necessary steps needed to enable the Spatialite extension using an RSQLiteConnection after which the get_postgis_query function works as normal.
One caveat, I have only tested this on Linux and these functions require the mod_spatialite library to be installed on the computer.