Pinning a result inserts a sql_workbench_result_snapshot row as a top-level
action. With QQQ core permission enforcement on, that insert is checked
against the session's permissions, and getUserPermissionNames() granted
only read/edit/delete on snapshots, so every user's pin was denied and
hosts had to grant the insert by hand. Record locks still limit snapshots
to the user's own notebooks.
New test: with enforcement on, the user permission set covers create,
update, run, pin, unpin and delete.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
james.maes
