Re: [Qgis-user] Updating a field set with default global variable on edit

On 8/22/17 3:36 PM, McDonaldR wrote: > Thanks Karl-Magnus > > > > We use triggers in the database already and they work perfectly but if > we want to record the specific user creating and editing features then > we’d have to create separate projects for each user. At the moment > the team of

Re: [Qgis-user] Updating a field set with default global variable on edit

An option in the layer properties to save without username and password? Or a possibility to change database connection for a layer? To one connection with another user or a connection with no user stored. Could be useful. Though it is efficient to use an text editor to change it always feels a

Re: [Qgis-user] Updating a field set with default global variable on edit

On Tue, 22 Aug 2017 15:45:17 +0200, Casper Bertelsen wrote: > Hi Ross, > > If you make your project without saving username and password, the > project will prompt for a user and password when opened. Then each > member can login using their assigned login and thus

Re: [Qgis-user] Updating a field set with default global variable on edit

Hi Casper, So nice to see you answering questions at the QGIS user list. Your knowledge is appreciated :) Lene Fischer Associate Professor University of Copenhagen Department of Geoscience and Natural Resource Management Forest and Landscape College Nødebovej 77a 3480 Fredensborg Denmark MOB

Re: [Qgis-user] Updating a field set with default global variable on edit

Hi All, to get field updates on vector layer edits (be they geometry or attribute edits) you can use the AutoFields plugin [1]. You can use expressions just like you do when setting default values in QGIS. Regards, Germán --- [1]

Re: [Qgis-user] Updating a field set with default global variable on edit

I love this mailing list. That is fantastic! We're testing this out right now and it seems to be working exactly as we need it. Thanks very much, Casper and Karl Magnus! Ross From: Qgis-user [mailto:qgis-user-boun...@lists.osgeo.org] On Behalf Of Casper Bertelsen Sent: 22 August 2017 14:45

Re: [Qgis-user] Updating a field set with default global variable on edit

Hi Ross, If you make your project without saving username and password, the project will prompt for a user and password when opened. Then each member can login using their assigned login and thus making it possible to use current_user in postgres. To remove saved username and password from

Re: [Qgis-user] Updating a field set with default global variable on edit

Thanks Karl-Magnus We use triggers in the database already and they work perfectly but if we want to record the specific user creating and editing features then we'd have to create separate projects for each user. At the moment the team of about 10 users all use a set of centrally stored

Re: [Qgis-user] Updating a field set with default global variable on edit

No, it's no big deal. That's why we are using it. And it's only one time per qgis session. Karl-Magnus Från: Qgis-user [mailto:qgis-user-boun...@lists.osgeo.org] För Casper Bertelsen Skickat: den 22 augusti 2017 14:34 Till: qgis-user@lists.osgeo.org Ämne: Re: [Qgis-user] Updating a field set

Re: [Qgis-user] Updating a field set with default global variable on edit

Hi too, Well logging into the QGIS-project should really be a big deal right ? - You only have to log in once no matter how many layers are loaded from the database. I have a table inside my QGIS project where I can create new users inside the database and administer

Re: [Qgis-user] Updating a field set with default global variable on edit

Hi! I've made the same things with triggers in the database. To avoid getting same username I've chosen not to save the username and password in the project. But then the user have to enter it every time the projects opens. If you can find a solution to your suggested approach it would be nice.

[Qgis-user] Updating a field set with default global variable on edit

Hi List, Anyone know how to update a field that has a global variable set as the default value when records are edited (geometry and/or attributes)? We have a QGIS project with a PostGIS layer loaded and configured with look-ups and relations so the users can update all the relevant fields.