QGIS » QGIS Application

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 -- [email protected]) to discuss funding a fix for this particular issue.

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

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.

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

Fair point Giovanni.

I would just like to get MySQL generally more supported because was it worked great not so long ago.
It worked very smoothly and such a shame to loose it.

The problem with my client is I want them to embrace GIS and they wont listen until I can show it working again.

I would just like to get MySQL generally more supported because was it worked great not so long ago.
It worked very smoothly and such a shame to loose it.

The problem with my client is I want them to embrace GIS and they wont listen until I can show it working again.

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!

Yes I can see I'm sounding like a lone voice in the wilderness.
My client won't budge until Mysql is supported and working out of the box.
MySQL is huge and I do so long to drop the ancient MapInfo.

MySQL is huge and I do so long to drop the ancient MapInfo.

is Spatial is tiny compared to PostgreSQL ;)