fix audit log container scoping test

[ankurjuneja]

Rationale

The Skyline audit log "Detailed Info" popup was broken, clicking it returned a 404 for most audit entries. This caused TargetedMSContainerScopingTest to fail.

The cause is a bug in the targetedms.AuditLog database view. It uses a recursive query that's supposed to walk the whole chain of audit entries for a document, but the recursion runs in the wrong direction. As a result, the view only ever returns the first entry in each chain instead of all of them.

The code that renders the detail popup looks up an entry by id, but the entry it needs is the last one in the chain, which the broken view never returns, so the lookup finds nothing and returns a 404.

The bug was introduced in 2022 by #502 (Issue 44507, "Allow audit log entries to belong to multiple runs"). That change flipped the query's starting point from the last entry to the first entry, but left the recursion walking in the old direction, so the two no longer matched. It has been latent ever since (the view definition is identical across 25.7, 25.11, and 26.3) and only surfaced now because the new audit-detail lookup relies on reaching entries the broken view drops.

This fix corrects the recursion direction so the view returns every entry in the chain. It also adds a schema upgrade step to rebuild the view on existing databases.

Related Pull Requests

• Issue 44507: Allow audit log entries to belong to multiple runs #502

Changes

• targetedms-create.sql — corrected the recursive CTE to walk root → children:
  JOIN logTree prev ON prev.entryHash = nxt.parentEntryHash. Verified fix returns the full tree (7516/7516 entries; both terminal entries reachable), so retrieve() resolves them.
• targetedms-26.008-26.009.sql (new) — drops the AuditLog view via fn_dropifexists so the corrected create.sql rebuilds it on existing installations (the drop/create pair only re-runs on a schema-version bump).
• TargetedMSModule.getSchemaVersion() — bumped to 26.009 to trigger the view recreation on upgrade.

[ankurjuneja]

The test passed - https://teamcity.labkey.org/buildConfiguration/LabKey_263Release_Premium_NightlyPostgres/4079057?buildTab=tests&status=all&name=TargetedMSContainerScopingTest&expandedTest=build%3A%28id%3A4079057%29%2Cid%3A2000000516

[ankurjuneja]

@labkey-jeckels do you want to create the same branch in 25.11 as well or just in 25.11 and it will merge forward?

[labkey-jeckels]

We've muted the failure in 25.11. Patching in 26.3 is good.

[labkey-jeckels]

This shouldn't be necessary, though it's harmless. Just the version bump should be enough to trigger the drop/create pair.