Re: [QGIS-Developer] Strange Mysql (spatial) behaviour: no points visible

2024-01-28 Thread Even Rouault via QGIS-Developer
Update: actually, instead of completely disabling server side spatial filtering with geographic SRS, I just found a hack... One can use ST_SRID() to hack a "random" projected CRS, and then things work So now the OGR mySQL driver will do things like: select MBRIntersects(ST_GeomFromText('POLYGO

Re: [QGIS-Developer] Strange Mysql (spatial) behaviour: no points visible

2024-01-28 Thread Even Rouault via QGIS-Developer
But, my point: why can QGIS apparently show attributes, while not showing a geom.. Apparently the features were fully retrieved. When displaying the attribute table, QGIS doesn't apply a spatial filter. Whereas when displaying features on the canvas, it does. And as I found out, something's

Re: [QGIS-Developer] Strange Mysql (spatial) behaviour: no points visible

2024-01-28 Thread Richard Duivenvoorde via QGIS-Developer
On 1/28/24 19:04, Even Rouault wrote: what I don't understand is how you manage to create with ogr2ogr a table without explicit SRS with features whose coordinates are not compatible of geographic coordinates. As mentioned previously, I do get a hard error from ogr2ogr when trying that. Which

Re: [QGIS-Developer] Strange Mysql (spatial) behaviour: no points visible

2024-01-28 Thread Even Rouault via QGIS-Developer
Richard, what I don't understand is how you manage to create with ogr2ogr a table without explicit SRS with features whose coordinates are not compatible of geographic coordinates. As mentioned previously, I do get a hard error from ogr2ogr when trying that. Which GDAL version do you use? Th

Re: [QGIS-Developer] Strange Mysql (spatial) behaviour: no points visible

2024-01-28 Thread Richard Duivenvoorde via QGIS-Developer
On 1/23/24 23:21, Even Rouault wrote: So all in all, no issues on my side... You were off course right :-) I found out how to fix the missing crs in mysql and wrote some info (for future reference) in a comment: https://github.com/qgis/QGIS/issues/55463#issuecomment-1913602140 One thing I

Re: [QGIS-Developer] Strange Mysql (spatial) behaviour: no points visible

2024-01-23 Thread Even Rouault via QGIS-Developer
Le 23/01/2024 à 20:43, Richard Duivenvoorde a écrit : Ah, oo :-) I can reproduce now in the docker! After seeing src/core/providers/ogr/qgsogrprovider.cpp:3236 : (crs) [0ms] no spatial reference found in the debug info of that other db, I thought to try to load the data WITHOUT telling it

Re: [QGIS-Developer] Strange Mysql (spatial) behaviour: no points visible

2024-01-23 Thread Richard Duivenvoorde via QGIS-Developer
Ah, oo :-) I can reproduce now in the docker! After seeing src/core/providers/ogr/qgsogrprovider.cpp:3236 : (crs) [0ms] no spatial reference found in the debug info of that other db, I thought to try to load the data WITHOUT telling it EPSG:31370: So instead of: ogr2ogr -update "mysql:tes

Re: [QGIS-Developer] Strange Mysql (spatial) behaviour: no points visible

2024-01-23 Thread Even Rouault via QGIS-Developer
I'll try to debug the current db, and I've asked the people to create a test db (which hopefully then has the same issue :-) ) I'm not familiar with MySQL but I guess there must be some dump & restore commands that could be used to exactly replicate a setup where the bug triggers? -- h

Re: [QGIS-Developer] Strange Mysql (spatial) behaviour: no points visible

2024-01-23 Thread Richard Duivenvoorde via QGIS-Developer
Thanks Even for checking Even! I replayed your test, and with me it was fine too My gut feeling is that it is something in the ogr - gdal bridge. OR there is a (?wkt) issue because of the move from an older mysql to a newer version? Is is actually exact the same issue as https://github.com/qgis/

Re: [QGIS-Developer] Strange Mysql (spatial) behaviour: no points visible

2024-01-23 Thread Even Rouault via QGIS-Developer
Richard, I've failed to reproduce. Here's my testing procedure: docker run --name gdal-mysql1 -e MYSQL_ROOT_PASSWORD=passwd -e "MYSQL_ROOT_HOST=%" -p 33060:3306 -d mysql:8.0.34 mysqld --default-authentication-plugin=mysql_native_password docker exec gdal-mysql1 sh -c "echo 'CREATE DATABASE tes

Re: [QGIS-Developer] Strange Mysql (spatial) behaviour: no points visible

2024-01-16 Thread Nyall Dawson via QGIS-Developer
On Wed, 17 Jan 2024 at 06:15, Alessandro Pasotti via QGIS-Developer < qgis-developer@lists.osgeo.org> wrote: > Hi Richard, > > sorry, no hints except to check the logs and the QGIS dev tools query > logger: is there anything suspicious? > There's a LOT of open bugs relating to mysql data -- eg ht

Re: [QGIS-Developer] Strange Mysql (spatial) behaviour: no points visible

2024-01-16 Thread Alessandro Pasotti via QGIS-Developer
Hi Richard, sorry, no hints except to check the logs and the QGIS dev tools query logger: is there anything suspicious? On Tue, Jan 16, 2024 at 8:08 PM Richard Duivenvoorde via QGIS-Developer wrote: > > No hints :-) ? > > I now have a live connection to the db, and can reproduce the issue here i

Re: [QGIS-Developer] Strange Mysql (spatial) behaviour: no points visible

2024-01-16 Thread Richard Duivenvoorde via QGIS-Developer
No hints :-) ? I now have a live connection to the db, and can reproduce the issue here in master on Linux too. It's really strange: have a local db, I can even copy features from the attribute table to my local table, and THEN they show up ogrinfo shows exactly the same information of the db

[QGIS-Developer] Strange Mysql (spatial) behaviour: no points visible

2024-01-12 Thread Richard Duivenvoorde via QGIS-Developer
Hi Devs, I was contacted by a company who after upgrading their db and QGIS did NOT see the points anymore. Note that 'all worked' when they used QGIS 3.10 (and an older mysql db) After a MySQL database upgrade, QGIS 3.10 was not able to connect anymore (apparently TLS issues), so they have to