Hey guys,
James just hit me with a question that I thought best to raise with you. When he upgrades a client Jiwa 6 to Jiwa 7, he ends up - on a case by case basis - with an extensive list of changes to be made, each time he runs through the upgrade. This is essentially a OneNote list he reads through and repeats in Jiwa. Inevitably, at 3am when doing the actual upgrade, a silly mistake snowballs into huge issues.
So his question "can you sniff the SQL updates as I make changes in Jiwa so that I can compile these into a script to re-run each test run".
While I can do this SQL-side, independently of Jiwa, the SQL is pretty noisy, and complicated by multiuser access. Better, if possible to do this Jiwa-side.
So my question - would it be possible, from a plugin, to intercept ALL database calls in order to log these? If so, then I can filter out INSERT/UPDATE/DELETE/EXECs and probably even annotate with the calling form. I would probably also work out some way of providing a logging on/off control, so that only specific UI-generated changes of interest are logged.
Is this at all possible, or am I barking up the wrong tree?
Cheers,
Neil