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

[Casper Bertelsen]

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 
reading/writing/admin-privileges.

Mvh. / Best regards
Casper Bertelsen

On 22/08/2017 13:34, Karl Magnus Jönsson wrote:
>
> 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.
>
> *Karl-Magnus *
>
> *Från:*Qgis-user [mailto:qgis-user-bounces at lists.osgeo.org] *För 
> *McDonaldR
> *Skickat:* den 22 augusti 2017 13:12
> *Till:* qgis-user at lists.osgeo.org
> *Ämne:* [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. There are also "*created_by*" and "*updated_by*" fields. These 
> are updated by a trigger in the database with the "*current_user*" 
> database variable. This works fine if you are the current user that 
> added the layer to the project - the trigger works perfectly.
>
> If you give the project to someone else and they create and edit 
> features in the layer the fields are still updated with your name as 
> you are the person who added the layer to the project. Not what we want.
>
> QGIS has global variables and there are some new ones - 
> *user_account_name* and *user_full_name* that can be set as default 
> values for the fields. When a new feature is created the field is 
> populated with the correct name. Which is what we want.
>
> However, when we update an existing record we'd like the 
> "*updated_by*" field to be updated with the current 
> "*user_account_name*". Like a trigger in the database would do on 
> update. Then we would have a better idea of the history of the feature.
>
> Ross
>
> *Ross McDonald | *GIS Data Coordinator | Angus Council, People, IT | 
> Angus House, Orchardbank Business Park, Sylvie Way, Forfar DD8 1AT*| 
> t: 01307 476419*
>
> This message is strictly confidential. If you have received this in 
> error, please inform the sender and remove it from your system. If 
> received in error you may not copy, print, forward or use it or any 
> attachment in any way. This message is not capable of creating a legal 
> contract or a binding representation and does not represent the views 
> of Angus Council. Emails may be monitored for security and network 
> management reasons. Messages containing inappropriate content may be 
> intercepted. Angus Council does not accept any liability for any harm 
> that may be caused to the recipient system or data on it by this 
> message or any attachment.
>
>
>
> _______________________________________________
> Qgis-user mailing list
> Qgis-user at lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-user/attachments/20170822/faaeb587/attachment.html>