Activity log for bug #298411
| Date | Who | What changed | Old value | New value | Message |
|---|---|---|---|---|---|
| 2008-11-15 14:49:30 | Christophe Vandeplas | bug | added bug | ||
| 2008-11-15 16:38:02 | Faraz Khan | zivios: importance | Undecided | Low | |
| 2008-11-15 16:38:02 | Faraz Khan | zivios: assignee | fkhan-zivios | ||
| 2008-11-15 16:38:02 | Faraz Khan | zivios: statusexplanation | Did it not give you an option to "rollback" the original failed transaction? If you let the rollback slide deleting a 'bad object' is not possible- hence the already exist errors. Maybe we should force rollback of a faulty transaction. | ||
| 2008-11-17 06:19:54 | Faraz Khan | zivios: status | New | Confirmed | |
| 2008-11-17 06:19:54 | Faraz Khan | zivios: statusexplanation | Did it not give you an option to "rollback" the original failed transaction? If you let the rollback slide deleting a 'bad object' is not possible- hence the already exist errors. Maybe we should force rollback of a faulty transaction. | You are absolutely correct. I left that part out since I didn't want there to be too much 'magic'. I will put in a configurable option for 'disabled automatic rollback on failure' so that the default mechanism is to rollback when a failure occurs. Otherwise- you have a corrupt ldap tree as you correctly noticed! | |
| 2009-05-25 10:33:43 | Faraz Khan | zivios: status | Confirmed | Fix Committed |
