-
-
Save iamphilrae/d538d5b48608de290bfee791df3e6f54 to your computer and use it in GitHub Desktop.
| @DATABASE@__%Y-%m-%d_%H-%M-%S |
Does anyone know why the @DATABASE@ variable would be empty when doing an export?
@SERVER@ @DATABASE@__%Y-%m-%d_%H-%M-%S
results in:
mysql_3306___2022-10-30_02-00-13.sql.gz
Does anyone know why the
@DATABASE@variable would be empty when doing an export?
@SERVER@ @DATABASE@__%Y-%m-%d_%H-%M-%Sresults in:
mysql_3306___2022-10-30_02-00-13.sql.gz
You could give __DB__ a try. I believe it's a legacy variable, and should output the same value as @DATABASE@, however you never know, may work.
@iamphilrae Thank you. I just gave it a shot, but unfortunately still no luck. :/
According to phpMyAdmin FAQ, @database@ refers to "the currently open database.
But since you are not "in" a database, it is not available.
Doesn't even work when you choose to export each database into its own file.
Weird, but that is phpMyAdmin's choice.
@JorgenBB Ahhhh, ok, that makes some sense, thank you.
It definitely is a strange decision, or perhaps just an oversight if they've never come across the issue themselves? It seems like a pretty easy thing to add, just getting the name of the db as it iterates through the list, and add it to a variable. I'm not much of a coder or I'd try submitting a PR myself. :/
@phpmyadmin team, please add this 'enhancement', I beeeegg you! QOL improvement to the n'th degree! :)
Thanks! ヾ(≧▽≦*)o
Thanks!