Bug #1049
date_mod enhanced management
| Status: | Closed | Start date: | ||
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | moyo | % Done: | 0% | |
| Category: | Common | |||
| Target version: | 0.71 |
Description
Should be able to blacklist some fields for which update should not change date_mod
Ex : last_login in glpi_users
Proposal :
- new property in class (have_date_mod : bool, date_mod_backlist : array)
- handle in commondb.
History
#1 Updated by moyo almost 13 years ago
To do :
Auto management of date_mod on update process :
Auto management of date_mod on update process :
- if date_mod is a field of the table
- if intersect of updates and blacklist array is not empty
- update date_mod
- else do not update date _mod
- if intersect of updates and blacklist array is not empty
Unable to auto manage on add process
#2 Updated by moyo almost 13 years ago
- Status changed from New to Closed