You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
in other words, the connection string is always an empty string and there is no way to use transaction groups when you have more than one GPKG in the same project.
That happens because QgsDataSourceUri( layer.source() ).connectionInfo() on a GPKG returns an empty string.
The sad reality is that QgsDataSourceUri is not appropriate anymore to handle all kind of data provider connections and URI encodings that we have.
The text was updated successfully, but these errors were encountered:
elpaso
added
the
Bug
Either a bug report, or a bug fix. Let's hope for the latter!
label
May 18, 2020
in other words, the connection string is always an empty string and there is no way to use transaction groups when you have more than one GPKG in the same project.
That happens because
QgsDataSourceUri( layer.source() ).connectionInfo()
on a GPKG returns an empty string.The sad reality is that QgsDataSourceUri is not appropriate anymore to handle all kind of data provider connections and URI encodings that we have.
The text was updated successfully, but these errors were encountered: