-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
r.tableCreate() not defined in JS #46
Comments
It makes sense to me to be able to support tableCreate and friends on the default db on the connection. BTW, eventually we'll add a dropdown to the data explorer that will denote the default database to run ops on. Moving to backlog though, because there are more important things to work out for now. |
The server change and ruby driver implementation are done. If Bill has time this could make 1.5 pretty easily. |
Is the short version for table_list included? I don't see such a change in 46_bare_tablecreate . Am I just looking at the wrong place? |
Whoops, yeah, missed that entirely. I'll add that tomorrow. |
(I'll update the ql2.proto file too.) |
Cool, thanks. -----Original Message----- Whoops, yeah, missed that entirely. I'll add that tomorrow. Reply to this email directly or view it on GitHub: |
table_list and updates to the .proto file are in the code-review |
@mlucy The JS and PY implementations have been pushed to branch 46_bare_tablecreate. |
@wmrowan: Awesome. I updated the code-review; this should be in next soon. |
This is now in next. |
So r.table('table_name') is a shortcut for r.db('test').table('table_name')
However, r.tableCreate('new_table') doesn't work in javascript (at least).
Can we have all methods after db() to work after r. by using the default database 'test'?
In that case, in the data explorer, I can suggest users r.table(), r.tableCreate(), r.tableDrop(), r.tableList() etc...
The text was updated successfully, but these errors were encountered: