12 Commits

Author	SHA1	Message	Date
Juergen E. Fischer	c6008b7ee1	fix MSVC build: reverts fee62e4, dff05dd and e3a77b9484c effectivly ... reverting 3fb0f66 (followup #45348) Using --no-public-is-protected (default on Windows) also works on Linux and fixes #45331 too	2021-10-21 23:03:48 +02:00
nirvn	ef84e48a09	Run sipify_all.sh	2021-10-12 16:34:05 +10:00
Denis Rouzaud	ec16736306	run sipify	2021-10-12 16:34:05 +10:00
Martin Dobias	1a8ff84791	[feature] Transactions in MSSQL provider	2021-09-09 08:07:21 -07:00
Denis Rouzaud	ba8a445850	run sipify	2021-03-22 21:13:52 +01:00
Nyall Dawson	50b9beaad6	[sipify] Catch more class references and insert :py:class: annotations	2021-01-31 05:41:22 +10:00
Nyall Dawson	b6d66becab	Sipify	2019-02-27 09:41:11 +10:00
Nyall Dawson	384d310233	Minor improvements to PyQGIS returns for SIP_OUT params	2019-02-05 04:55:34 +11:00
Denis Rouzaud	166e952c33	run sipify	2018-12-19 08:04:27 -04:00
Denis Rouzaud	edfb7e1465	run sipify	2018-12-18 17:17:25 -04:00
Even Rouault	6a987f913b	[OGR provider] [FEATURE] Add support for transactions on GPKG databases ... For complete support, it requires two GDAL fixes: - One to avoid feature count to be invalid when using ROLLBACK TO SAVEPOINT f73ec8cd1d - Another one to avoid nasty issues, at least on Linux, with the POSIX advisory locks used by libsqlite that could be invalidated due to how GDAL could open files behind the back of libsqlite. The consequence of this could be the deletion of -wal and -shm files, which caused issues in QGIS (non working iterators when the edit is finished, and later edits in the same session not working). Those issues could appear for example if doing ogrinfo on the .gpkg opened by QGIS, or if opening two QGIS session on the .gpkg Both fixes are queued for GDAL 2.3.1	2018-06-15 12:56:59 +02:00
Denis Rouzaud	7df2593caf	move auto generated sip file in dedicated folder	2018-05-14 10:23:37 -04:00