Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

uniqe names vs casesensetivity #58

Open
elbenfreund opened this issue Apr 5, 2016 · 0 comments
Open

uniqe names vs casesensetivity #58

elbenfreund opened this issue Apr 5, 2016 · 0 comments

Comments

@elbenfreund
Copy link
Collaborator

Right now, category names are case sensitive and unique. This in itself is not a problem.
However, if we later come to decide that search is to be case insensetive, we may up with several results for one search string despite the uniqueness constraint.

We will have to decide if this is desired behavior and we deal with multiple results or if it is preferable to enforce "case insensitive uniqueness" and avoid such subtleties.

@elbenfreund elbenfreund added this to the 0.2 backwards compatibility release milestone Apr 5, 2016
@elbenfreund elbenfreund modified the milestones: 0.0.2 , 0.0.3, 0.0.4 Apr 7, 2016
@elbenfreund elbenfreund modified the milestones: 0.10.0, 0.11.0, 0.12.0 Apr 19, 2016
@elbenfreund elbenfreund modified the milestones: 0.12.0, 0.13.0 Jul 21, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant