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

Console - case insensitive lead to database lost with Studio #7327

Closed
StarCmd opened this issue Apr 10, 2017 · 2 comments
Closed

Console - case insensitive lead to database lost with Studio #7327

StarCmd opened this issue Apr 10, 2017 · 2 comments
Assignees
Milestone

Comments

@StarCmd
Copy link

StarCmd commented Apr 10, 2017

OrientDB Version: v2.2.16

Java Version: 1.7.0_67

OS: macOS 10.11.6

Expected behavior

Studio (orientDB server ?) should not be confused by using Upper or Lower case within the console.

Actual behavior

while working in lowercase within Console, the Studio home page update it's database list with a case sensitive name of the same database. Deleting the lower case one, also delete the upper case one.

Steps to reproduce

  1. Studio : Create a new TEST database (uppercase)
  2. Console : connect remote:localhost/test admin admin
  3. Console : orientdb {db=test}> import database somedata.json
  4. Check database folders : GratefulDeadConcerts, OSystem, TEST
  5. Studio : dropdown databases list = TEST, test, GratefullDeadConcerts
  6. Studio : select "test" then the Trashcan icon (Drop the selected database)
  7. Studio : dropdown databases list = TEST, GratefullDeadConcerts
  8. Check database folders : GratefulDeadConcerts, OSystem
@lvca lvca added the bug label Apr 14, 2017
@wolf4ood
Copy link
Member

It's not related to studio i think it's a storage issue

Only from console

create database remote:localhost/TEST root root plocal
connect remote:localhost/test admin admin 
disconnect
connect remote:localhost root root     
list databases 

I get

Found 3 databases:

* test (plocal)
* TEST (plocal)
* GratefulDeadConcerts (plocal)

Forwarding to Storage Team

@wolf4ood wolf4ood removed their assignment Apr 14, 2017
@wolf4ood
Copy link
Member

Hi @StarCmd
it has be fixed by this
#7358

Thanks

@wolf4ood wolf4ood added this to the 2.2.19 milestone Apr 26, 2017
@santo-it santo-it added duplicate and removed bug labels Apr 26, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

4 participants