View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0000753XMB1Bugspublic2025-01-03 18:232025-07-10 16:23
Reportermiqrogroove Assigned Tomiqrogroove  
PrioritynormalSeverityminorReproducibilityN/A
Status resolvedResolutionfixed 
Product Version1.9.8 SP3 
Target Version1.10.00Fixed in Version1.10.00 
Summary0000753: Why is Table Truncation Specified in Prune Code?
DescriptionThe 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.
TagsNo tags attached.
MySQL Version
PHP Version
Web Server
Browser
Flags
Original Reporter
SVN Revision
Git Commithttps://github.com/miqrogroove/xmb/commit/0ad528e94c742b42be32f580c57e181084905520

Activities

There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2025-01-03 18:23 miqrogroove New Issue
2025-01-03 18:25 miqrogroove Description Updated
2025-07-10 14:28 miqrogroove Assigned To => miqrogroove
2025-07-10 14:28 miqrogroove Status new => assigned
2025-07-10 14:51 miqrogroove Product Version => 1.9.8 SP3
2025-07-10 16:23 miqrogroove Status assigned => resolved
2025-07-10 16:23 miqrogroove Resolution open => fixed
2025-07-10 16:23 miqrogroove Fixed in Version => 1.10.00
2025-07-10 16:23 miqrogroove Git Commit => https://github.com/miqrogroove/xmb/commit/0ad528e94c742b42be32f580c57e181084905520