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
Table name issue system is case-insensitive but tableCreate is case-sensitive #822
Comments
This is in code review 553. I noticed while testing this that the web UI won't let you create the table "foo" if you already have a table "Foo". We should change that to behavior too just for consistency sake. |
Reassigning to myself. |
K. This is in essence assigned to both of us since I haven't actually committed my part to next yet but whatever we all know what's going on here. |
Just to be sure: |
Yup.
|
Done in 52d5343 |
Yup it's in next. I just tried testing the webUI and it still wasn't letting me make tables with names that only differed in capitalization. I tried to do |
Err, I'm a moron, I forgot to push on github -_- I can confirm that it works fine. |
r.tableCreate('bar')
r.tableCreate('Bar')
The query language happily creates both tables, but the cluster immediately raises an issue that there is a name conflict.
After some discussion with @jdoliner and @mlucy and @srh we decided to fix the issue resolution system to be case-sensitive.
The text was updated successfully, but these errors were encountered: