Debugging a blackbox is challenging when a developer lacks access to the bug report, which contains sensitive user data. This is not uncommon, most commercial software, such as Windows and Office, generate anonymized bug reports from users' personal desktops, and they promise that user privacy will not be compromised.
However, in the realm of databases, blackbox debugging becomes significantly more difficult. The basic idea of this project is twofold: (i) using operators that transform a database into an encrypted version, enabling developers to examine its running states, and (ii) replacing user data with equivalent data classes (this concept exists in software engineering testing, where two inputs produce the same coverage and trigger the same bug).
An intriguing aspect of this work is its compilation of numerous common actions taken by database administrators (DBAs) and translating them into actionable insights, potentially opening doors for further research. One exciting possibility is to explore automatic local debugging using these insights, which eliminates the need for human involvement and addresses concerns about data breaches.