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

Ignore extraneous field attributes when generating database migrations #1941

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

Originally created by @jeremystretch on GitHub (Aug 15, 2018).

Proposed Changes

Exclude certain field attributes from analysis when making migrations:

  • verbose_name
  • help_text
  • choices
  • Possibly others

This should be doable by overriding the makemigrations management command.

Justification

Django has an annoying habit of generating migrations when model fields are altered, even if those changes don't result in any modifications to the database schema. For example, modifying the help_text on a model field will trigger a migration, even though it obviously has no effect on the database. This is especially annoying when updating choice fields, such as Interface.form_factor: Each modification to the list of choices triggers a migration, yet the list of choices is not actually conveyed as a constraint on the table.

Originally created by @jeremystretch on GitHub (Aug 15, 2018). ### Proposed Changes Exclude certain field attributes from analysis when making migrations: * `verbose_name` * `help_text` * `choices` * Possibly others This should be doable by overriding the `makemigrations` [management command](https://github.com/django/django/blob/master/django/core/management/commands/makemigrations.py). ### Justification Django has an annoying habit of generating migrations when model fields are altered, even if those changes don't result in any modifications to the database schema. For example, modifying the `help_text` on a model field will trigger a migration, even though it obviously has no effect on the database. This is especially annoying when updating choice fields, such as `Interface.form_factor`: Each modification to the list of choices triggers a migration, yet the list of choices is not actually conveyed as a constraint on the table.
adam added the status: acceptedtype: housekeeping labels 2025-12-29 17:20:45 +01:00
adam closed this issue 2025-12-29 17:20:45 +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 status: accepted type: housekeeping
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#1941
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?