Hi all,
if I run a command as
ogrinfo ./db.sqlite -sql "SELECT ST_Cutter(NULL, 'a', NULL, NULL, 'b', NULL, 'out', 1, 1);"
am I introducing significant bottlenecks?
Is it always better to run it via sqlite?
echo "SELECT ST_Cutter(NULL, 'a', NULL, NULL, 'b', NULL, 'out', 1, 1);" | sqlite3 ./db.sqlite
Or are they somehow almost coincident?
Thank you
On Wed, 30 Dec 2020 00:18:26 -0800 (PST), Andrea Borruso wrote:
> Hi all,
> if I run a command as
>
> ogrinfo ./db.sqlite -sql "SELECT ST_Cutter(NULL, 'a', NULL, NULL,
> 'b',
> NULL, 'out', 1, 1);"
>
> am I introducing significant bottlenecks?
>
> Is it always better to run it via sqlite?
>
> echo "SELECT ST_Cutter(NULL, 'a', NULL, NULL, 'b', NULL, 'out', 1,
> 1);" | sqlite3 ./db.sqlite
This (spatialite specific) command will probably fail, since the spatialite extension has not been loaded.ogrinfo should load the spatialite extension when needed.The same is true if you replace 'sqlite3' with the 'spatialite' command tool.