This is more efficient if there are a huge number of old login attempt because
it avoid to fetch the ids and to have loop over them to delete.
issue5377
review24901002
The login data comes from an unauthenticated user so it could be very large and
thus fill the database. But indeed we don't need to have the full login to get
the LoginAttempt benefit, just the 1024 starting char is enough.
issue5381
review17901002
We convert all the fields that were storing python code into PYSON.
We add a pyson attribute on field tag to store PYSON value.
issue4416
review6971002
There is an access rule on ir.session so user can only see his own session.
So it needs to use the root user to compute for others.
issue4558
review10201002
The changeSet 2a7d6a7e5c59 modified the returning of get()
method of Many2Many fields, from dictionary of list to dictionary of tuples.
issue4542
review14971002
* Model and Field access checked only if _check_access is set
* Add check_access to RPC
* Add check_access to Wizard and Report
issue4081
review8481002
- Adds menu entry for ir.model.data
- Remove write access on ir.model.data to administrator group
- Add sync button on ir.model.data
- Change storage format of values to be comparable
issue3918
review8351002
If bcrypt is not available, it fallbacks to sha1 but it will use bcrypt to hash
new password if available.
The storage uses a simple hashing scheme which eases to add new hashing method
and doesn't rely anymore on the specific Sha field but on Function field.
Thanks to Vishesh Yadav
review1039002
The call to _get_preferences makes some processing based on the user of the
context.
In order for those computations to return the right value the context must be
set when instanciating the user.
issue3068
review1711002
Cédric Krier