Skip to content

Conversation

@anshul98ks123
Copy link
Collaborator

@anshul98ks123 anshul98ks123 commented Apr 14, 2025

Issue(s)

Currently, the unique namespace constraint doesn't work as expected for NULL namespace
because MySQL doesn’t support direct UNIQUE constraint over nullable columns to also reject multiple NULLs

This can result into situations where multiple rows can exist for NULL namespace
which can break multiple parts of the system

Description

This PR fixes the issue by making the namespace column non null, adding uniqueness constraint over it and also updates the existing NULL namespace rows with NULL value namespace

@vercel
Copy link

vercel bot commented Apr 14, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
thirdeye ✅ Ready (Inspect) Visit Preview 💬 Add feedback Apr 14, 2025 10:00am

@anshul98ks123 anshul98ks123 force-pushed the TE-fix-namespace-entity-constraints branch from e0a815a to b622908 Compare April 14, 2025 09:44
@anshul98ks123 anshul98ks123 changed the title Te fix namespace entity constraints [peristence] Disallow multple namespace configuration entities with same namespace Apr 14, 2025
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.

2 participants