View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000753 | XMB1 | Bugs | public | 2025-01-03 18:23 | 2025-01-03 18:25 |
| Reporter | miqrogroove | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | N/A |
| Status | new | Resolution | open | ||
| Target Version | 1.10.00 | ||||
| Summary | 0000753: Why is Table Truncation Specified in Prune Code? | ||||
| Description | The logic of the Prune feature escapes me. Most of the business logic falls under: if (count($queryWhere) > 0) Then it shows an else block with multiple table truncation. However, I don't think it's possible to reach the else block. Earlier in the script it has this fallback with a comment on it: $queryWhere[] = '1=0'; //Neither 'prune by' option was set, prune should abort. Given that logic and the combinational context, I don't think the table truncation commands are needed or relevant anymore. If that's all accurate, then the "prune should abort" code should be changed to an error template to be consistent with how the rest of the feature works. | ||||
| Tags | No tags attached. | ||||
| MySQL Version | |||||
| PHP Version | |||||
| Web Server | |||||
| Browser | |||||
| Flags | |||||
| Original Reporter | |||||
| SVN Revision | |||||
| Git Commit | |||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-01-03 18:23 | miqrogroove | New Issue | |
| 2025-01-03 18:25 | miqrogroove | Description Updated |
