Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change backups filenames to YYYYMMDD #791

Closed
1 task done
MrChocolatine opened this issue Feb 24, 2024 · 0 comments · Fixed by #874
Closed
1 task done

Change backups filenames to YYYYMMDD #791

MrChocolatine opened this issue Feb 24, 2024 · 0 comments · Fixed by #874

Comments

@MrChocolatine
Copy link
Contributor

MrChocolatine commented Feb 24, 2024

Describe your suggested feature

Hello and thank you for your app.

Currently, backup file names use this format:

kotatsu_DDMMYYY.bk.zip

which gives, for instance if using today:

kotatsu_24022024.bk.zip

However, this format messes up their listing when files are sorted by name.

For instance, if I have these backup files (created automatically or manually):

kotatsu_01012023.bk.zip
kotatsu_10012023.bk.zip

kotatsu_01012024.bk.zip

Once sorted by name and in ascending/descending order we get:

// ascending order

kotatsu_01012023.bk.zip
kotatsu_01012024.bk.zip
kotatsu_10012023.bk.zip

// descending order

kotatsu_10012023.bk.zip
kotatsu_01012024.bk.zip
kotatsu_01012023.bk.zip

Could you please change the name of the backup files by using the following format:

kotatsu_YYYYMMDD.bk.zip

That way, the previous list of backups would be corrected listed:

// ascending order

kotatsu_20230101.bk.zip
kotatsu_20230110.bk.zip
kotatsu_20240101.bk.zip

// descending order

kotatsu_20240101.bk.zip
kotatsu_20230110.bk.zip
kotatsu_20230101.bk.zip

Thank you.

Acknowledgements

  • I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant