Michael Dieringer 89f648928f Give the table-relation-test fixtures a real relation to exclude and one to protect ... The "Category Code" field had no TableRelation at all, so the good subscriber's RemoveTableRelation call targeted metadata that never existed - a no-op. Added a real TableRelation to "Sample Setup" on that field (the one known exception to exclude) and a second, ordinary self-referencing relation ("Parent No." -> "Sample Header"."No.") with no exception. The good fixture now removes only the first; the bad fixture's table-wide removal (field/related table/field all 0) now demonstrably also strips the second, showing the actual anti-pattern instead of removing nothing meaningful.		2026-09-22 20:59:56 +02:00
..
knowledge	Give the table-relation-test fixtures a real relation to exclude and one to protect	2026-09-22 20:59:56 +02:00
skills	Fix four merge-critical issues from Jesper's 2026-09-22 review	2026-09-22 14:35:48 +02:00