starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-12 13:30:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Implement a mechanism for maintaining denormalized (cached) database fields #6760

New Issue
Closed
opened 2025-12-29 19:45:08 +01:00 by adam · 0 comments
adam commented 2025-12-29 19:45:08 +01:00
Owner
Copy Link

Originally created by @jeremystretch on GitHub (Aug 2, 2022).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v3.3-beta1

Feature type

New functionality

Proposed functionality

Establish a mechanism for registry denormalized model fields within the application so that they can be kept up-to-date. (These are fields which store cached values from elsewhere in the database.) The registry can be used to track these fields, and we can leverage Django signals to trigger automatic updates in the event of a change.

#9902 could also help with this effort, although I don't believe it's strictly required.

Use case

Sometimes it is necessary to denormalize certain database fields for performance optimization and/or to enable filtering. For example, the CableTermination model introduced in v3.3 caches the device, rack, location, and site associated with its termination object.

Database changes

This feature should not require any database changes itself.

External dependencies

No response

Originally created by @jeremystretch on GitHub (Aug 2, 2022). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v3.3-beta1 ### Feature type New functionality ### Proposed functionality Establish a mechanism for registry denormalized model fields within the application so that they can be kept up-to-date. (These are fields which store cached values from elsewhere in the database.) The registry can be used to track these fields, and we can leverage Django signals to trigger automatic updates in the event of a change. #9902 could also help with this effort, although I don't believe it's strictly required. ### Use case Sometimes it is necessary to denormalize certain database fields for performance optimization and/or to enable filtering. For example, the CableTermination model introduced in v3.3 caches the device, rack, location, and site associated with its termination object. ### Database changes This feature should not require any database changes itself. ### External dependencies _No response_
adam added the status: acceptedtype: featurebeta labels 2025-12-29 19:45:08 +01:00
adam closed this issue 2025-12-29 19:45:08 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label beta status: accepted type: feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#6760
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?