> So you assume to have grants to write in the table where is stored the published informazioni. This is not always true. The dba amministratore of a published environment not like to have some cowboy to write into its DBMS.
It depends on the access you need. If you're in an environment with an actual dba, they can give you the rights you need and no more. The more widespread case is when you're acting as your own DBA and in which case you can have the rights you need. The user QGIS Server uses doesn't need to be the same user that has update access. There are many solutions. It also depends on the application, and a billion other things that make it difficult to say "you can't do that". It _can_ be done, it's just a matter of making it happen. > Instead in low profile environment where there is 1 user only and it is webadmin , qgis user and perhaps also publisher. Not always it ha also the capability to admin a DBMS like postgres. I'm not sure what you're getting at. No one is saying that the db-based projects should be the only, or even the default, method. > I feat that this option increasing complexity will reduce the installation of qgis-server. Again, no one is talking about removing the current method. I'm not sure what your problem is with people discussing a more complex, but also extremely flexible, needed, and wanted method of storing projects. If you don't want it, don't use it. No one is taking away file-based projects. Jim On Wed, Aug 12, 2015 at 10:03 AM, Andrea Peri <aperi2...@gmail.com> wrote: > So you assume to have grants to write in the table where is stored the > published informazioni. > This is not always true. The dba amministratore of a published environment > not like to have some cowboy to write into its DBMS. > > Instead in low profile environment where there is 1 user only and it is > webadmin , qgis user and perhaps also publisher. Not always it ha also the > capability to admin a DBMS like postgres. > > I feat that this option increasing complexity will reduce the installation > of qgis-server. > > A. > Il 12/ago/2015 03:29 PM, "James Keener" <j...@jimkeener.com> ha scritto: > >> I was also looking for this a bit back and never found a solution. I >> ended up using other software, unfortunately. >> >> As for being less flexible, it is exactly as flexible as a qgs file would >> be, it's just that they could be manipulated and created more easily. I >> would love to see the parts of the file broke out in the database and not >> just using a single text blob, though. >> >> Also, setting up identical-enough is fairly trivial, especially if most >> of the layers are already coming from a database, or known cache of >> shapefiles. >> >> Jim >> >> On Wed, Aug 12, 2015 at 9:13 AM, Andrea Peri <aperi2...@gmail.com> wrote: >> >>> I don't guess is more flexible. >>> Infact usually the teting environment is never exactly exals to the >>> publish environmnet. >>> >>> A file allw to open and correct the paths from develop and publish >>> environment. >>> Also the svg symbols could be not exactly with the same path from >>> develop and publish environment. >>> >>> So having a same project in a db is more complex becasue need to have >>> two environment exactly the same. >>> And this is not possible. >>> . >>> >>> I guess the db storing for project could be more flexible only if the >>> paths to the layers and relative paths of svg was not stored in the >>> project file but instead in other files. >>> >>> My 2ct. >>> >>> A. >>> >>> >>> 2015-08-12 15:06 GMT+02:00 lars lingner <gislars+l...@gmail.com>: >>> > Hello, >>> > >>> > I'm looking for a solution for storing QGis project files (qgs) in a >>> > PostgreSQL database. Storing the files in a table isn't actually the >>> > problem, but getting it out and feeding it to QGis server. >>> > >>> > Did anyone had this need already? Would this be a good idea? >>> > >>> > In my use case the project files are generated, based on a default >>> > project file. Having the file in the DB would give more flexibility. >>> > >>> > Since saving the style in DB is already supported by QGis, I'm just >>> > curious of opinions of other users or developers. >>> > >>> > Thanks in advance for any feedback >>> > >>> > Lars >>> > _______________________________________________ >>> > Qgis-user mailing list >>> > Qgis-user@lists.osgeo.org >>> > http://lists.osgeo.org/mailman/listinfo/qgis-user >>> >>> >>> >>> -- >>> ----------------- >>> Andrea Peri >>> . . . . . . . . . >>> qwerty àèìòù >>> ----------------- >>> _______________________________________________ >>> Qgis-user mailing list >>> Qgis-user@lists.osgeo.org >>> http://lists.osgeo.org/mailman/listinfo/qgis-user >>> >> >>
_______________________________________________ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user
