OGRLayer::WriteArrowBatch() and CreateFeature() mutually exclusive in the same session

Chris Toney via gdal-dev <[email protected]>
Newsgroups gmane.comp.gis.gdal.devel
Message-ID <CALRbqOQq+CLZ7pBN1Q=jmmJauEr7zFkFfEcR98hsgKb7w=6N0w@mail.gmail.com>
Hi,
I'm trying to understand implications of OGRLayer::WriteArrowBatch():

>This method and CreateFeature() are mutually exclusive in the same session.

The context is binding code where the user could potentially call
either of these methods at any point during the session.

Does "session" refer to the layer or dataset instance, or the GDAL
session itself?

In tests with GPKG, using WriteArrowBatch() followed by
CreateFeature() worked and didn't cause any obvious problems. Should
binding code guard against this in general?

Similarly, CreateFieldFromArrowSchema() and CreateField() are mutually
exclusive in the same session. Is there any issue with using
CreateField() and WriteArrowBatch() in the same session?

Thanks.

Chris
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.