#413 When changing databases, keep the "same" table open

Git
closed-wont-fix
nobody
None
5
2017-02-20
2014-06-20
No

Feature request: when changing between databases, if the newly selected database has the a table with the same name as the previously opened table from the previous database, then open that table.

In other words, follow these steps:
1. Login to adminer and open the database "foobar".
2. Select/describe/open the table "footable".
3. Now use the drop-down box to select the database "test_foobar".
4. HERE:
- The current behavior will just open the "homepage" for the database "test_foobar".
- My proposed new behavior is:
- - If there is a table named "footable" in "test_foobar", then open it [i.e., open the same view (select/describe/whatever) in "test_foobar.footable", just like it was opened in "foobar.footable"]
- - If there is not such table, then keep the current behavior, opening the database homepage.

Discussion

  • avimar

    avimar - 2016-08-10

    I undertand why you'd want this -- that example of moving into the test database.
    But I can easily forsee people accidentally switching into their production database and not realize it, since it reselected the table automatically.

    In the meantime, you can manually edit the URL to switch the DB, which will leave the table selection -- or even the entire query -- intact.

     
  • Jakub Vrána

    Jakub Vrána - 2017-02-20
    • status: open --> closed-wont-fix
     
  • Jakub Vrána

    Jakub Vrána - 2017-02-20

    This would be quite complicated to implement properly. Namely, Adminer doesn't know if the table exists in the target database before switching there. If not then it shouldn't display an error but redirect to the database homepage instead.

    Also, it could be confusing.

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks