New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mysql connection not working #29241
Comments
Author Name: Nyall Dawson (@nyalldawson) Hi Steve, Unfortunately I think MySQL isn't widely used as a spatial database format, which is why this bug report hasn't seen any activity (we all know there's countless high-priority bugs in this queue!). It remains to be seen if this is a QGIS bug or is a bug in the underlying GDAL library which is used to access MySQL data. I would suggest if this is a high-priority issue for your workplace that it's worth getting in touch with a QGIS support provider (or email me direct -- nyall@north-road.com) to discuss funding a fix for this particular issue. |
Author Name: steve smith (steve smith) Hi Nyall, Thanks for reading the post and I do see your problem of prioritising the bug list. I will try making connections with GDAL and see if the issue is there. Here now is my pitch for MySQL - hope you read on ! The MySQL/Mariadb (Mariadb being the open source clone of MySQL) spatial support has been there for some years now and has become very stable. MySQL/Mariadb is now the most used database in the world (topping even Oracle) and is used in all Apache/PHP stacks and a great way for adding "where is the nearest" functions to web applications. QGIS actually works great with Mariadb and QGIS handles is so smoothly but I will never get my corporate client to switch from Mysql just for me. Thanks if you are still reading, Steve |
Author Name: Giovanni Manghi (@gioman)
As Nyall suggested, if your client is a corporate and needs to use qgis+mysql then it can have a great professional support, just choose one among https://qgis.org/en/site/forusers/commercial_support.html |
Author Name: Giovanni Manghi (@gioman)
|
Author Name: steve smith (steve smith) Fair point Giovanni. I would just like to get MySQL generally more supported because was it worked great not so long ago. The problem with my client is I want them to embrace GIS and they wont listen until I can show it working again. |
Author Name: Giovanni Manghi (@gioman)
at times regressions happen, and when is about a feature that is used a by a lot of people then there is also a lot of interested in having it fixed asap. The support for Mysql in QGIS does not seems (at least to me) to have ever been a need for many. In such cases the interested corporate/administrations/etc should step in instead of waiting a fix/implementation done/supported bu others. Cheers! |
Author Name: steve smith (steve smith) Yes I can see I'm sounding like a lone voice in the wilderness. |
Author Name: Giovanni Manghi (@gioman)
is Spatial is tiny compared to PostgreSQL ;) |
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Giovanni Manghi (@gioman)
|
will this ever be fixed? |
Author Name: steve smith (steve smith)
Original Redmine Issue: 21424
Affected QGIS version: 3.6.0
Redmine category:data_provider
We have just upgraded to 3.6 but sadly we still cannot connect to MYSQL versions after 5.7 (Mariadb 10 is fine)
It's the same problem : no features appear until a layer filter is set and then editing is disabled.
Could this be because mysql dropped intersects() function in favour of MBR_intersects() and ST_intersects ?
We can provide connections for anyone who might debug this.
This is such a shame as this blocks us from using qgis as our corporate GIS.
Thanks in advance,
Steve Smith
Related issue(s): #28383 (relates)
Redmine related issue(s): 20563
The text was updated successfully, but these errors were encountered: