cubicweb #914464 last login time fails on ldap users [resolved]

when a user from ldap logs on a CW app, we get the following stack trace in the logs:

2010-04-27 07:55:02 - (cubicweb.repository) ERROR: unexpected error while executing SET X last_login_time NOW WHERE X eid %(x)s with {'x': 2164}
Traceback (most recent call last):
 File "c:\Documents and Settings\alf\My Documents\Pylos\cubicweb\server\repository.py", line 582, in execute
   build_descr)
 File "c:\Documents and Settings\alf\My Documents\Pylos\cubicweb\server\querier.py", line 652, in execute
   results = plan.execute()
 File "c:\Documents and Settings\alf\My Documents\Pylos\cubicweb\server\querier.py", line 161, in execute
   result = step.execute()
 File "c:\Documents and Settings\alf\My Documents\Pylos\cubicweb\server\ssplanner.py", line 580, in execute
   repo.glob_update_entity(session, edef, set(self.attributes))
 File "c:\Documents and Settings\alf\My Documents\Pylos\cubicweb\server\repository.py", line 1107, in glob_update_entity
   source.update_entity(session, entity)
 File "c:\Documents and Settings\alf\My Documents\Pylos\cubicweb\server\sources\ldapuser.py", line 568, in update_entity
   raise RepositoryError('this source is read only')
RepositoryError: this source is read only

This is noise, and we should avoid it as it is known that ldap users cannot have their last login time updated.

priorityimportant
typebug
done in3.8.3
load0.200
load left0.000
closed by#72679e450f6d [web] dont attempt to update last login time on ldap users, avoiding spurious tb in logs (closes #914464)