MYSQL Connection with wrong tables

[qgib]

Author Name: Gerd Dreier (Gerd Dreier)
Original Redmine Issue: 17538
Affected QGIS version: 2.18.14
Redmine category:data_provider/ogr

---

In former times MYSQL Connection from a table as saved in the QGS File as:

  <datasource>MySQL:OrkanDB,host=Server,port=3306,user=webuser,password=xxxx,tables=gewstation|layername=gewstation</datasource>

Now it is saved as:

  <datasource>MySQL:OrkanDB,host=Server,port=3306,user=webuser,password=xxxx|layerid=93</datasource>

If I add or insert a table in the database from Mysql, the layerid will be changed an QGIS connect with an other table.
To save the connection to a table over the layerid is not a good idea. In former Times it was better!

[qgib]

Author Name: Giovanni Manghi (@gioman)

---

Do you know what was the last release were it worked as expected?

---

• regression was changed from 0 to 1
• status_id was changed from Open to Feedback
• priority_id was changed from Normal to High
• crashes_corrupts_data was changed from 1 to 0

[qgib]

Author Name: Gerd Dreier (Gerd Dreier)

---

Sorry, i don't know the release, but I update periodically. So it was changed between Feb. 2016 and March 2017.

[qgib]

Author Name: Alessandro Pasotti (@elpaso)

---

• category_id was changed from Data Provider to Data Provider/OGR

[qgib]

Author Name: Alessandro Pasotti (@elpaso)

---

It would be useful if you could confirm this bug on master. IIRC there were some recent changes in the way sublayers are referred to in OGR provider.

[qgib]

Author Name: Even Rouault (@rouault)

---

I'm pretty sure this is a known issue that has been fixed in the QGIS 3 line. Previously for multi-layer datasources, the project stored them with a layer index, which was unstable if the datasource had layers removed or added. QGIS3 now stores the layer name instead.
Closing as fixed in QGIS 3

---

• resolution was changed from to fixed/implemented

[qgib]

Author Name: Even Rouault (@rouault)

---

• status_id was changed from Feedback to Closed