Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Check whether the new referencedAt is "null safe" #10214

Open
snazy opened this issue Jan 16, 2025 · 0 comments
Open

Check whether the new referencedAt is "null safe" #10214

snazy opened this issue Jan 16, 2025 · 0 comments
Assignees
@snazy

Comments

@snazy
Copy link
Member

snazy commented Jan 16, 2025

Issue description

It's likely not causing problems in production, but an incorrect handling could render the "purge unused objects" not working.

Background: upgrade scenario with referencedAt being null (think SQL =? vs IS NULL).
@snazy snazy self-assigned this Jan 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@snazy snazy

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@snazy