Open candlerb opened 1 year ago
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.
Whoops, I removed the status tag by mistake.
NetBox version
v3.4.8
Feature type
Change to existing functionality
Proposed functionality
Introduced in v3.4.0: "Device and virtual machine names are no longer case-sensitive"
Should this be extended to other models which have unique constraints on name, in particular Site and Tag?
Use case
Same reason as doing this on devices and VMs: for data validation purposes.
It seems weird to allow site "foo bar" and "Foo bar" as two different sites, when site names are supposedly "unique".
Database changes
I believe enforcement is via a database btree index
External dependencies
None