Feature request #1127
PostGIS default Styles should be saveable in system qgis.db
Status: | Closed | ||
---|---|---|---|
Priority: | Low | ||
Assignee: | |||
Category: | Map Legend | ||
Pull Request or Patch supplied: | Resolution: | fixed | |
Easy fix?: | No | Copied to github as #: | 11187 |
Description
To deliver unified style definitions from PostGIS repository to distributed users it would be great
to have the chance to define a global style definition stored in share/qgis/qgis.db. The search
path could be ~/.qgis/qgis.db prior share/qgis/qgis.db. In this way the single user has
the ability to define personal style definitions.
Associated revisions
introduce separate qml databases for fileless datasources (fixes #1127)
git-svn-id: http://svn.osgeo.org/qgis/trunk/qgis@8777 c8812cc2-4d05-0410-92ff-de0c093fc19c
introduce separate qml databases for fileless datasources (fixes #1127)
git-svn-id: http://svn.osgeo.org/qgis/trunk@8777 c8812cc2-4d05-0410-92ff-de0c093fc19c
History
#1
Updated by Jürgen Fischer over 16 years ago
- Status changed from Open to In Progress
#2
Updated by Jürgen Fischer over 16 years ago
waiting for feature freeze to pass.
#3
Updated by Tim Sutton over 16 years ago
Hi
I have some reservations as to whether its desirable for end users to edit the qgis.db. For one thing you may encounter issues e.g. when doing apt-get upgrade and apt tries to overwrite the db with a new version. I think the feature request is a valid one but we should think about other approaches to the solution too before applying the patch.
#4
Updated by Jürgen Fischer over 16 years ago
Replying to [comment:4 timlinux]:
Hi
I have some reservations as to whether its desirable for end users to edit the qgis.db. For one thing you may encounter issues e.g. when doing apt-get upgrade and apt tries to overwrite the db with a new version. I think the feature request is a valid one but we should think about other approaches to the solution too before applying the patch.
Yup. The patch only searches the global qgis.db for styles. Transfering styles in to the database is not covered, this would need to be done manually.
It might be better to have seperate style databases and search them in the following order:
<pre> <pre> That way the user can update his own style database until it fits and then copy it to the projects directory and rename it accordingly or copy it to the global directory.
#5
Updated by Jürgen Fischer over 16 years ago
- Status changed from In Progress to Closed
- Resolution set to fixed
#6 Updated by Anonymous over 15 years ago
Milestone Version 1.0.0 deleted