Skip to content

Settings and activity

1 result found

  1. 67 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Anonymous supported this idea  · 
    An error occurred while saving the comment
    Anonymous commented  · 

    I really LOVE this product. But today, I needed to rename a database because I like to do so when I create a backup. 1) Backup the database 2) Create a new database and restore from the backup 3) Rename the old (working) version as _OLD, and 4) Rename the New copy as the original.

    This way, I am absolutely ensured that my old backup is a working version, as any new work has been done to a valid copy of it.

    I am quite amazed that I cannot do this with this AMAZING product! Why does dbForge for MySQL(MariaDB) have this limitation? Do I need to upgrade to something more than the Standard Edition for this? Or does the entire product line have this limitation?

    Is there any chance you can implement this feature in the near future in the Standard Edition?

    Thank you!