Skip to content
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

Disable saving styles to database for renderers that are not supported #24830

Closed
qgib opened this issue Jul 26, 2017 · 4 comments
Closed

Disable saving styles to database for renderers that are not supported #24830

qgib opened this issue Jul 26, 2017 · 4 comments
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Symbology Related to vector layer symbology or renderers

Comments

@qgib
Copy link
Contributor

qgib commented Jul 26, 2017

Author Name: shenriod - (shenriod -)
Original Redmine Issue: 16931
Affected QGIS version: 2.18.11
Redmine category:symbology


New description:
Now all symbology renderes seems that are suitable to allow saving the style inside a DB. To avoid errors messages the option for them should be disabled.

Old description:
I have created a new Geopackage layer: @layer > Create Layer > New Geopackage Layer@,then added a few other layers (@save as...@)

I now want to save a default style in the Geopackage DB but I get this error message: "Unable to save layer style. It's not possible to create the destination table on the database"

Not sure if someone else can reproduce this behavior?


@qgib
Copy link
Contributor Author

qgib commented Jul 26, 2017

Author Name: shenriod - (shenriod -)


!Selection_854.png!


  • 11274 was configured as MyGeoPackageLayer.gpkg
  • 11275 was configured as Selection_854.png

@qgib
Copy link
Contributor Author

qgib commented Jul 26, 2017

Author Name: Giovanni Manghi (@gioman)


Just tested on 2.18.11 on Ubuntu 16.04 and works ok. Maybe it depends on the style you are trying to save, would you mind attach it? thanks.


  • status_id was changed from Open to Feedback
  • category_id was changed from Data Provider to Symbology

@qgib
Copy link
Contributor Author

qgib commented Sep 25, 2017

Author Name: Giovanni Manghi (@gioman)


  • subject was changed from Unable to save a style in a Geopackage to Disable saving styles to database for renderers that are not supported
  • operating_system was changed from Ubuntu 17.04 to
  • status_id was changed from Feedback to Open
  • description was changed from I have created a new Geopackage layer: @layer > Create Layer > New Geopackage Layer@,then added a few other layers (@save as...@)

I now want to save a default style in the Geopackage DB but I get this error message: "Unable to save layer style. It's not possible to create the destination table on the database"

Not sure if someone else can reproduce this behavior? to New description:
Now all symbology renderes seems that are suitable to allow saving the style inside a DB. To avoid errors messages the option for them should be disabled.

Old description:
I have created a new Geopackage layer: @layer > Create Layer > New Geopackage Layer@,then added a few other layers (@save as...@)

I now want to save a default style in the Geopackage DB but I get this error message: "Unable to save layer style. It's not possible to create the destination table on the database"

Not sure if someone else can reproduce this behavior?

@qgib
Copy link
Contributor Author

qgib commented Mar 9, 2019

Author Name: Giovanni Manghi (@gioman)


End of life notice: QGIS 2.18 LTR

Source:
http://blog.qgis.org/2019/03/09/end-of-life-notice-qgis-2-18-ltr/

QGIS 3.4 has recently become our new Long Term Release (LTR) version. This is a major step in our history – a long term release version based on the massive updates, library upgrades and improvements that we carried out in the course of the 2.x to 3x upgrade cycle.

We strongly encourage all users who are currently using QGIS 2.18 LTR as their preferred QGIS release to migrate to QGIS 3.4. This new LTR version will receive regular bugfixes for at least one year. It also includes hundreds of new functions, usability improvements, bugfixes, and other goodies. See the relevant changelogs for a good sampling of all the new features that have gone into version 3.4

Most plugins have been either migrated or incorporated into the core QGIS code base.

We strongly discourage the continued use of QGIS 2.18 LTR as it is now officially unsupported, which means we’ll not provide any bug fix releases for it.

You should also note that we intend to close all bug tickets referring to the now obsolete LTR version. Original reporters will receive a notification of the ticket closure and are encouraged to check whether the issue persists in the new LTR, in which case they should reopen the ticket.

If you would like to better understand the QGIS release roadmap, check out our roadmap page! It outlines the schedule for upcoming releases and will help you plan your deployment of QGIS into an operational environment.

The development of QGIS 3.4 LTR has been made possible by the work of hundreds of volunteers, by the investments of companies, professionals, and administrations, and by continuous donations and financial support from many of you. We sincerely thank you all and encourage you to collaborate and support the project even more, for the long term improvement and sustainability of the QGIS project.


  • resolution was changed from to end of life
  • status_id was changed from Open to Closed

@qgib qgib closed this as completed Mar 9, 2019
@qgib qgib added Bug Either a bug report, or a bug fix. Let's hope for the latter! Symbology Related to vector layer symbology or renderers labels May 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Symbology Related to vector layer symbology or renderers
Projects
None yet
Development

No branches or pull requests

1 participant