SFSQL and SFSQL_PG driver for lazy_tbl #2
Closed
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.
SFSQL()
wraps the basic sql query toread_sf()
, passing in the DSN argument in the usual way (file, url, connection string) with a dummylayer
value.SFSQL_PG()
adds another level to allow input of host,dbname,user,password which is passed down as the 'PG:...' connection string toSFSQL()
.There is a lot I haven't considered, readonly is ignored, security/obfuscation on the connection string is ignored, and no detail on the difference between DB-drivers and non-DB:
i.e. DB drivers have the SQL passed in direct, so it is engine-specific, otherwise for non-DB afaik:
_ogr_geometry_
whether selected or not (see next comment)Discussed here: mdsumner/RGDALSQL#7
Other:
Examples, first pseudocode for postgresql
Examples with SHP and GPKG