Ticket #1337 (closed defect: fixed)
Some modules appears as changed after making a backup
| Reported by: | javier.amor.garcia@… | Owned by: | jamor@… |
|---|---|---|---|
| Milestone: | 2.2 | Component: | base |
| Severity: | normal | Keywords: | |
| Cc: |
Description (last modified by juruen@…) (diff)
I have sen this with the events and objects modules.
Moved for post 1.4
Attachments
Change History
comment:2 Changed 4 years ago by javier.amor.garcia@…
a call to EBox::DataTable::ids() mark the modules as cahnged. This call is made to get the files for the row's elements which need to been backed up.
comment:4 Changed 4 years ago by juruen@…
- Milestone changed from 1.2 (stable release) to 1.1.10 (alpha2)
comment:6 Changed 3 years ago by juruen@…
- Description modified (diff)
- Milestone changed from 1.4 to nice to have someday
Events is the module that makes this happen
comment:12 Changed 2 years ago by jamor@…
Possible explanation:
1) framework call ids() when looking for EBox::Types::File to backup
2) soem tables had a syncRows() which modifies things thus marking the module a changes
comment:13 Changed 2 years ago by jamor@…
- Status changed from assigned to closed
- Resolution set to fixed
comment:14 Changed 2 years ago by jamor@…
The last commit fioxes monitor module but this problem could arise in a module which have a DataTable? whith a EBox::Type::File or EBox::Type::HasMany? with a foreignModel with EBox::Type::File AND a syncRows method which fires, adding/removing rows