Skip to content

Meta: replace by-mid cleanup with schema-owned deletion - #274

Merged
JJJ merged 1 commit into
masterfrom
jjj/fix-262-meta-schema-deletion
Sep 25, 2026
Merged

JJJ merged 1 commit into
masterfrom
jjj/fix-262-meta-schema-deletion

Conversation

@JJJ

@JJJ JJJ commented Sep 25, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • make MetaStore the explicit ownership boundary for item-meta cleanup
  • derive BerlinDB-owned meta row and object columns from the registered Schema
  • keep WordPress-owned metadata on the metadata API so hooks and cache invalidation are preserved
  • cover nonstandard row/object columns, UUID object IDs, per-key WordPress hooks, and cached reads

Testing

  • composer validate --strict --no-check-publish
  • vendor/bin/phpstan analyse --memory-limit=1G
  • vendor/bin/phpcs
  • bin/run-tests.sh -p 8.1 -w 6.7 -- --group default
  • bin/run-tests.sh -p 8.2 -w 6.7 -- --group default

Fixes #262.

Treat MetaStore as the ownership boundary for item-meta cleanup. BerlinDB-owned stores now resolve their row and object columns from the registered Schema, while WordPress-owned metadata continues through the metadata API so hooks and cache invalidation retain their expected behavior.

Fixes #262.
@JJJ
JJJ merged commit a22276b into master Sep 25, 2026
6 checks passed
@JJJ
JJJ deleted the jjj/fix-262-meta-schema-deletion branch September 25, 2026 07:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Meta: replace by-mid cleanup with schema-owned deletion

1 participant