Skip to content

Extend case-insensitive uniqueness constraints #12318

@candlerb

Description

@candlerb

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

Metadata

Metadata

Assignees

Labels

complexity: mediumRequires a substantial but not unusual amount of effort to implementnetboxstatus: acceptedThis issue has been accepted for implementationtype: featureIntroduction of new functionality to the application

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions