Le 06/02/2025 à 12:30, Deyan Vasilev a écrit :
Hello,
it may be needed for sure for the whole session or at least if you
need the already registered extension to be available at the next db
open attempt.
A deeper look in sqlite3 gave me the sqlite3_shutdown() API that
actually frees the extension attached via
sqlite3_reset_auto_extension() together with various other sqlite3
stuff. I do not see GDAL to call sqlite3_shutdown() anywhere and I
think it is quite reasonable to do it in some GDAL sqlite driver
finalization steps - in the OGRSQLiteBaseDataSource destructor, in the
Close() method after closing db, etc.
GDAL is just a library. It may be integrated in an application that
would use sqlite3 itself, and GDAL calling sqlite3_shutdown(), could
case chaos in the application.
--
http://www.spatialys.com
My software is free, but my time generally not.
_______________________________________________
gdal-dev mailing list
gdal-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/gdal-dev
