Add EventTarget.project_name
#3362
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Return the project name for all targets in `/api/events/list`. Required for displaying event targets and building entity URLs in the UI. Implemented by joining event targets with projects. The performance effect of the join are tolerable — with a dataset of 1.8 million events, requests with various filters take about 0.05s with hot Postgres cache, and up to ~0.75s with cold cache, which is similar to previous measurements.
r4victor
approved these changes
Dec 10, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Return the project name for all targets in
/api/events/list. Required for displaying eventtargets and building entity URLs in the UI.
Implemented by joining event targets with
projects. The performance effect of the join are
tolerable — with a dataset of 1.8 million events,
requests with various filters take about 0.05s
with hot Postgres cache, and up to ~0.75s with
cold cache, which is similar to previous
measurements.
Part of #3290