Feature request #4322
Store projects in databases
|Pull Request or Patch supplied:||No||Resolution:|
|Easy fix?:||No||Copied to github as #:||14259|
The idea is to be able to store projects within a central database system.
In a bigger multi-user working scenario, layers are stored within a centralized postgres database.
On the other hand, the environment to access those centralized databases is stored independently locally.
When considering that many of the users of the system might not know anything how the database is organized, it might happen that such users could change properties related to the viewing and editing of those tables jeopardizing correctness of the tables.
In my precise use case, I helped someone define a complex layout of geo tables and relations. After that we created a project with all of the subtleties, on how such tables would be edited and viewed.
Everything perfect up until now ! ;-)
The problem was that we needed to distribute this project through all of its users, and although distribution is problematic, it is even more problematic that its users can modify the project.
For example, imagine a layer that is originally configure to show a combo box (Value Map) with two elements, any of its users can access that same property, edit it, change the value map and start producing mistakes that only very late might be detected.
Using the databases, it might be possible to distribute projects as well as check for permissions on editing its features.
#3 Updated by Cupertino Miranda over 7 years ago
Sorry but I don't seem to understand why someone would actually pay lots of money for such feature and why it makes software overly complex.
A very basic implementation of such feature could be to simply to create a table with a name::text and content::text in the database, where the content would be the .qgs xml code.
So, same functions that would load and save the project can actually load it, but instead, taking the xml from a table row.
Regarding the non editable project, I still wasn't able to take a look at the code, so I cannot really argue on such feature.
I think you assume this feature would be what geodatabases are in ESRI tools, but from my understanding geodatabases are redundant when using postgres, and in fact over complex to be implemented. IMHO geodatabases, when using postgres or other database engines, seem irrelevant.