On 7 June 2017 at 21:20, johnrobot wrote:
> Hi
> There is no additional code. I didn´t expect the first example to work, but
> I do consider the crash a bug. I get the same result in QGIS 2.14.6 on
> Windows 7. I will open a ticket for it.
Likely what's happened is you've run this in the Python c
Hi
There is no additional code. I didn´t expect the first example to work, but
I do consider the crash a bug. I get the same result in QGIS 2.14.6 on
Windows 7. I will open a ticket for it.
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/QGIS-2-18-9-crash-using-Python-cons
On mercredi 7 juin 2017 13:09:53 CEST Tobias Wendorff wrote:
> Am Di, 6.06.2017, 22:11 schrieb Even Rouault:
> > Renaming the layers in ArcMap probably fixed the case inconsistency.
> >
> > Fixed per https://trac.osgeo.org/gdal/ticket/6916
>
> I don't know, if .gpkg allows UTF8 characters in colu
Am Di, 6.06.2017, 22:11 schrieb Even Rouault:
>
> Renaming the layers in ArcMap probably fixed the case inconsistency.
>
> Fixed per https://trac.osgeo.org/gdal/ticket/6916
I don't know, if .gpkg allows UTF8 characters in column name.
Doesn't lower() introduce problems with UTF8? Some characters m
