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

Improve admin table page URL #2365

Open
pilwon opened this issue May 7, 2014 · 5 comments
Open

Improve admin table page URL #2365

pilwon opened this issue May 7, 2014 · 5 comments
Milestone

Comments

@pilwon
Copy link

pilwon commented May 7, 2014

How about improving the URL to one of:

  • /#tables/<table-name>
  • /#tables/<db-name>/<table-name>
  • /#databases/<db-name>/<table-name>
  • /#db/<db-name>/<table-name>

instead of /#tables/<table-uuid>?

@neumino
Copy link
Member

neumino commented May 7, 2014

That could be possible, but there is a tricky case.

Two tables can have the same name (and belongs to the same database). You have a name conflict in this case, but that's still a possible state in the cluster.

@pilwon
Copy link
Author

pilwon commented May 7, 2014

@neumino Why was it necessary to allow duplicate table names in the same database?

@neumino
Copy link
Member

neumino commented May 7, 2014

@pilwon -- we don't allow it, but it can happen because of some race conditions or netsplits.

@mlucy
Copy link
Member

mlucy commented May 7, 2014

@pilwon -- it isn't intended behavior, the problem is that in a distributed system you sometimes have the same event happen in two places. If two nodes in the cluster both create a table test, you end up with two tables named test, and you have to resolve the conflict in the web UI before you can access them in the drivers by writing r.table('test'). The web UI needs to be able to deal with these conflicting tables, so it always refers to tables by their UUID, which is unique.

@pilwon pilwon changed the title Improve table page URL in Admin UI Improve admin table page URL May 7, 2014
@coffeemug coffeemug added this to the subsequent milestone May 7, 2014
@coffeemug
Copy link
Contributor

Moving to subsequent since this is tricky to do and think through.

@danielmewes danielmewes modified the milestones: backlog, subsequent Mar 24, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants