Opened 14 years ago
Last modified 14 years ago
#3335 closed defect
CopyLayer() method should use transactions similar to ogr2ogr — at Version 1
| Reported by: | rdewit | Owned by: | chaitanya |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | OGR_SF | Version: | unspecified |
| Severity: | normal | Keywords: | CopyLayer |
| Cc: |
Description (last modified by )
Copying from any data source to SQLite (at least in Python) is painfully slow when you don't explicitly use transactions.
The generic implementation of the OGRDataSource::CopyLayer() method for a data source should use transactions in a similar way to ogr2ogr by default, and have an option with similar functionality to -gt in ogr2ogr to control how many features are in a transaction.
See discussion here: http://lists.osgeo.org/pipermail/gdal-dev/2010-January/023220.html
Change History (1)
comment:1 by , 14 years ago
| Component: | PythonBindings → OGR_SF |
|---|---|
| Description: | modified (diff) |
| Keywords: | CopyLayer added |
| Owner: | changed from to |
Note:
See TracTickets
for help on using tickets.
Chaitanya,
Please implement this when convenient.