feat(event_tags): Add event_tags table and migration script #349
+105
−13
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This pull request introduces a new
event_tags
table and its associated migration script. By expanding and indexing the contents of the tags field of the events table in the events_tags table in advance, the search process by REQ can be made much faster than the original JSONB operation.Related Issue
#348
Motivation and Context
The addition of the
event_tags
table is required to efficiently manage and query event tag data. This change aims to improve data organization and access, facilitating better event management within the application.How Has This Been Tested?
The changes have been tested in a local development environment. I performed the following tests:
event_tags
table.event_tags
table and verified its integrity.Types of changes
Checklist: