-
Notifications
You must be signed in to change notification settings - Fork 14
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
Listing Personal Tables #94
Comments
I this is no longer a problem, can you please check (not the bin folder should reflect the changes as well) |
I'm still seeing a strange list of tables when I try to tab complete |
Oh I see, Maybe there is something I messed up creating the CACHE_* tables. I'll take a look, it might be a synonymous issue as well. To give some context, CACHE_* has the tables only visible by me, i.e., your public tables since I'm the one populating that CACHE table, in the tab will appears those tables plus the your own table list (without prefix). Maybe there is something wrong with those tables, but nevertheless the tables from one DB shouldn't be mixed up with the other DB. Thanks! I'll take a look |
Ok, sort of makes sense. My guess with the tables that I can't find anywhere is that they are in the recycling bin or have otherwise been dropped but not purged. However, I looked in the recycling bin and didn't find them. |
I fixed the CACHE_* columns and this will not longer be an issue |
I've noticed some strange behavior with tab completing and explicitly accessing my personal tables. I find that strange things happen when I prepend my username.
Here are my tables on DESSCI
Here is what happens when I try to tab complete starting with my username.
Some of these tables are my public tables from DESOPER, but I'm not sure where the others (e.g.,
Y2Q2_OBJECTS_V0
) reside. They are not listed from DESOPERInterestingly, from DESOPER, I get a different list of tables when I try to tab complete, but they appear to match my personal tables in DESOPER.
However, trying to tab complete without my username prefix fails
The text was updated successfully, but these errors were encountered: