Skip to content

[Bug]: Bookmark 'regression' #20198

@Gaibhne

Description

@Gaibhne

Describe the bug

We just upgraded a relatively ancient PMA instance and noticed that something we considered a feature, but might have just been unintentional functionality stopped working: having a bookmark with a blank database used to, just like with a blank user name, be considered "make available in all databases".

As we, like presumably many people, have dozens and dozens of near-identical databases for different projects/customers, that was a great feature, because it meant we didn't have to copy and paste thousands and thousands of bookmarks (bookmark count times DB count).

This seems to be 'fixed' the current version, likely due to reworking of how the queries work. It would be a relatively minor change (Bookmark::getList and Bookmark::get, unless I missed one) to allow this behavior again, though there are no UI elements for this.

If there is interest in this, I would be happy to make a PR, with maybe a UI element to allow it as a second step if and when the feature passes review and is merged, but I don't want to waste the time if this is something that is actively unwanted and was removed intentionally.

phpMyAdmin version

5.2.3

Metadata

Metadata

Assignees

No one assigned

    Labels

    BugA problem or regression with an existing feature

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions