When trying to reproduce http://hub.qgis.org/issues/10485, I noticed a regression.
Now attribute table no longer shows features with OGR GeometryCollection.
Fixes also issues where sublayer geometry type is too strict regarding 2D vs 2.5D
geometry types.
Fixes#15675
In the case where we deal with a shapefile, it is possible that it has
pre-existing holes in the DBF (see #15407), so if using a GDAL version
recent enough (>=2.1.2) to have reliable packing, do a packing at the
first edit action.
Fixes#15407
Refs #15393 and #15570
Real fix for the REPACK issues has been committed per
GDAL ticket https://trac.osgeo.org/gdal/ticket/6672 (GDAL 2.1.2 or above)
Add test to simulate the situations that caused problems.
all open child panel widgets
Avoids the stack state becoming inconsistent because child
panel widgets from a different main panel are still present
And add unit tests for QgsPanelWidgetStack
The order of the elements is irrelevant and duplicate elements are unwanted. It
is therefore a perfect candidate for a set instead of a list. This prevents
filtering for duplicates manually be replacing some filer codes with (more
performant) builtin methods of QSet.
The OGC PropertyIsLike element can have 4 attributs:
* matchCase to specify LIKE or ILIKE
* wildCard to specify a wildcard char symbol
* signleChar to specify a single char symbol
* escape to specify an escape char symbol
This method is also doing case insensitive "fuzzy" matching now, this
just adds yet another level of tolerance.
This changes the expressions to also take the alias into account if no
matches have been found.
The Expression LIKE binary operator does not care about escape % and _ char.
No-one has already open an issue about it but in the OGC element PropertyIsLike the user can defined is own wild and single char. This mean that QGIS has to escape % and _ if they are not used as wild and single char.
- Local server searches for a free port before binding
- Server tests now ignore attributes order
- Updated reference docs
- Renamed projects ("+" -> "_")
- Added a smoke test for auth manager and WMS/WFS providers
Fixed the add relation functionnality: the table is sorted. When the code
was setting the sorted column, the row was sorted and the other columns it was
setting were set on the wrong row.
Previously when using the multiline option for text edit widgets
the entire contents of the field would be discarded if the entered
value exceeded the maximum length for a string field.
Now the entered string is truncated to the maximum field length.
Concurrent read and write can lock a GeoPackage database given
the default journaling mode of SQLite (delete). Use WAL when
possible to avoid that.
Fixes#15351
