Thanks! Adding the ReleaseResultSet call was my next adjustment after
reviewing some of my C++ code. I was just examining if Dispose was
sufficient to clean up or if I needed to explicitly call ReleaseResultSet.
--
Sent from: http://osgeo-org.1560.x6.nabble.com/GDAL-Dev-f3742093.html
___
On lundi 10 juin 2019 10:19:26 CEST jkellio2 wrote:
> Just in case anyone was curious. The issue here was in the way I was reading
> the result set layer the first time. I only read 1 feature (as that was all
> I was interested in). Evidently that leaves the result set in a busy state.
> I needed t
Just in case anyone was curious. The issue here was in the way I was reading
the result set layer the first time. I only read 1 feature (as that was all
I was interested in). Evidently that leaves the result set in a busy state.
I needed to either read the entire layer, i.e.
OSGeo.OGR.Featur
In C# the using statement calls Dispose for you. I've stepped through the
OGR C# code and confirmed that Dispose is called.
The database locked error occurs in the
OGRGeoPackageTableLayer::SyncToDisk() method on the call
RunDeferredCreationIfNecessary(). I drilled down to that method and SQLite
On mercredi 5 juin 2019 05:38:32 CEST jkellio2 wrote:
> I'm using the OGR/GDAL C# managaged API to write to a GeoPackage database
> and I keep running into a "database is locked" error when I try to sync the
> database to disk. After much experimentation, this appears to only happen
> if I first o
I'm using the OGR/GDAL C# managaged API to write to a GeoPackage database and
I keep running into a "database is locked" error when I try to sync the
database to disk. After much experimentation, this appears to only happen
if I first open the GeoPackage to do a read, close the db (Dispose the
Dat
