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

Increasing max. field lengths #1494

New Issue
Closed
opened 2025-12-29 16:32:27 +01:00 by adam · 1 comment
adam commented 2025-12-29 16:32:27 +01:00
Owner
Copy Link

Originally created by @taka-psba on GitHub (Jan 11, 2018).

Issue type

[x] Feature request
[ ] Bug report
[ ] Documentation

Environment

  • Python version: 2.7.5
  • NetBox version: 2.2.7

Hi

I see here that you're generally happy with 64 character field limits, but we have things like:

  • tenants (curr. max. 30):
    • "Department of Science Information Technology and Innovation" (59 chars)
    • "Department of Justice and Attorney General (42 chars)
  • sites (curr. max. 50):
    • "Rockhampton Central Region Police Communications Centre and Police Station" (74 chars)
    • "Moa Island - St Pauls Community - Torres Strait Island Police Support Office" (76 chars)
  • interfaces (curr. max. 64):
    • "Microsoft Network Adapter Multiplexor Driver-Microsoft Load Balancing/Failover Provider-0000" (92 chars)
    • "HP Ethernet 1Gb 4-port 331FLR Adapter #3-WFP 802.3 MAC Layer LightWeight Filter-0000" (84 chars)
    • "Intel(R) PRO/1000 MT Network Connection #2-Network Load Balancing Filter Driver-0000" (84 chars)

I'm importing stuff from an existing NMS, and since I can't really make changes to the source data, I've put in a translation layer for problematic values, but things like "Department of Science Information Technology and Innovation" had to be compressed down to "Dept. of Sci.Info.Tech.Innov.", which is not really acceptable to the client :-)

Any chance of these field lengths being increased?

Thanks

Originally created by @taka-psba on GitHub (Jan 11, 2018). ### Issue type [x] Feature request <!-- An enhancement of existing functionality --> [ ] Bug report <!-- Unexpected or erroneous behavior --> [ ] Documentation <!-- A modification to the documentation --> <!-- Please describe the environment in which you are running NetBox. (Be sure to verify that you are running the latest stable release of NetBox before submitting a bug report.) If you are submitting a bug report and have made any changes to the code base, please first validate that your bug can be recreated while running an official release. --> ### Environment * Python version: 2.7.5 * NetBox version: 2.2.7 Hi I see [here](https://github.com/digitalocean/netbox/issues/894#issuecomment-283676826) that you're generally happy with 64 character field limits, but we have things like: - tenants (curr. max. 30): - "Department of Science Information Technology and Innovation" (59 chars) - "Department of Justice and Attorney General (42 chars) - sites (curr. max. 50): - "Rockhampton Central Region Police Communications Centre and Police Station" (74 chars) - "Moa Island - St Pauls Community - Torres Strait Island Police Support Office" (76 chars) - interfaces (curr. max. 64): - "Microsoft Network Adapter Multiplexor Driver-Microsoft Load Balancing/Failover Provider-0000" (92 chars) - "HP Ethernet 1Gb 4-port 331FLR Adapter #3-WFP 802.3 MAC Layer LightWeight Filter-0000" (84 chars) - "Intel(R) PRO/1000 MT Network Connection #2-Network Load Balancing Filter Driver-0000" (84 chars) I'm importing stuff from an existing NMS, and since I can't really make changes to the source data, I've put in a translation layer for problematic values, but things like "Department of Science Information Technology and Innovation" had to be compressed down to "Dept. of Sci.Info.Tech.Innov.", which is not really acceptable to the client :-) Any chance of these field lengths being increased? Thanks
adam closed this issue 2025-12-29 16:32:27 +01:00
adam commented 2025-12-29 16:32:28 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 11, 2018):

The field lengths will not be increased. These values are included in object tables, and it would be ridiculous to have such long descriptors mangling the rendering of tables. I suggest using abbreviations for the names and including the long form, if necessary, in the object description or comments.

@jeremystretch commented on GitHub (Jan 11, 2018): The field lengths will not be increased. These values are included in object tables, and it would be ridiculous to have such long descriptors mangling the rendering of tables. I suggest using abbreviations for the names and including the long form, if necessary, in the object description or comments.
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
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#1494
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?