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

Migrate Advisory aliases from JSON field to M2M relationship #1777

Open
keshav-space opened this issue Feb 12, 2025 · 0 comments · May be fixed by #1784
Open

Migrate Advisory aliases from JSON field to M2M relationship #1777

keshav-space opened this issue Feb 12, 2025 · 0 comments · May be fixed by #1784
Assignees
@keshav-space

Comments

@keshav-space
Copy link
Member

Filtering based on the advisory aliases is excruciatingly slow due to the JSON field.
@keshav-space keshav-space self-assigned this Feb 12, 2025
@keshav-space keshav-space changed the title Convert Advisory aliases from JSON field to M2M relationship Migrate Advisory aliases from JSON field to M2M relationship Feb 12, 2025
@keshav-space keshav-space linked a pull request Feb 21, 2025 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@keshav-space keshav-space

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Migrate Advisory aliases field to M2M relationship aboutcode-org/vulnerablecode
1 participant
@keshav-space