BDS-1085Save query no longer gives path
save query no longer gives the path to the file, which breaks scripts. The description of save query in how_to.html did not change to specify this, and it doesn't seem like a good behavior anyways. What if another file with the same name exists in another dir? Likely not, but it's bad on principle. Please fix this and issue a bug fix update specifically for BDS. Also, fix your affected versions.
Ex: $world/db/014698.ldb is now $world/014698.ldb
Script: MCBEbackup.sh Commit d2ff4b032310d8f9958c07890ca6081c1ceb368a works around this
Environment
Ubuntu Server 18.04.2
Created Issue:
save query no longer gives path
save query no longer gives the path to the file, which breaks scripts. The description of save query in how_to.html did not change to specify this, and it doesn't seem like a good behavior anyways. What if another file with the same name exists in another dir? Likely not, but it's bad on principle. Please fix this and issue a bug fix update specifically for BDS. Also, fix your affected versions.
Ex: $world/db/014698.ldb is now $world/014698.ldb
Script: MCBEbackup.sh
Environment
Ubuntu Server 18.04.2, version is 1.12.0.28, please fix your affected version list.
save query no longer gives the path to the file, which breaks scripts. The description of save query in how_to.html did not change to specify this, and it doesn't seem like a good behavior anyways. What if another file with the same name exists in another dir? Likely not, but it's bad on principle. Please fix this and issue a bug fix update specifically for BDS. Also, fix your affected versions.
Ex: $world/db/014698.ldb is now $world/014698.ldb
Script: MCBEbackup.shCommit
save query no longer gives the path to the file, which breaks scripts. The description of save query in how_to.html did not change to specify this, and it doesn't seem like a good behavior anyways. What if another file with the same name exists in another dir? Likely not, but it's bad on principle. Please fix this and issue a bug fix update specifically for BDS. Also, fix your affected versions.
Ex: $world/db/014698.ldb is now $world/014698.ldb
Script: MCBEbackup.shCommit
save query no longer gives the path to the file, which breaks scripts. The description of save query in how_to.html did not change to specify this, and it doesn't seem like a good behavior anyways. What if another file with the same name exists in another dir? Likely not, but it's bad on principle. Please fix this and issue a bug fix update specifically for BDS. Also, fix your affected versions.
Ex: $world/db/014698.ldb is now $world/014698.ldb
Script: MCBEbackup.sh Commit d2ff4b032310d8f9958c07890ca6081c1ceb368a works around this
![[Mojang] Mega_Spud (Jay Wells)](../../../data/avatars/users/92696.png){kind=small}
I run my bedrock server in memory (slow hard disks, fast computer) so I rely on save scripts to keep/restore changes. This problem cost me a couple days of changes before I caught it.
Everything is exactly as described above. (Ubuntu server, BDS version 1.12.0.28). Seems like a strange oversight.
I've ran across this issue in 1.14.20 as well
Full path is given as of 1.16.0.2, the deed is done, the bug is fixed.
How does having the full path help? Is there any way to automate the backup of these files?
Full path not from root, but from world. As said in the bug report:
Ex: $world/db/014698.ldb is now $world/014698.ldb
Automating the backup as seen in the script in the bug report can be done.