-
Notifications
You must be signed in to change notification settings - Fork 4
Corrected the A+B+C.zip file naming convention #8
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
base: 2.0
Are you sure you want to change the base?
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -31,8 +31,10 @@ Whenever you sync with the server, a file with the format `{date in GMT}={X}+{Y} | |
| {date in GMT}={B}+{Y}.zip | ||
|
|
||
| **Resulting transaction file** | ||
| Because `date in GMT of the oldest` < `date in GMT of the youngest`, | ||
| {date in GMT}={X}+{Y}+{Z}.zip | ||
| Resulting transaction file Based on alphabetical order, say if `X < Y`, then: {date in GMT}={X}+{Y}+{Z}.zip | ||
| Hence, in all P+Q+R.zip type filenames, alphabetically `P < Q` | ||
|
||
|
|
||
| Any transaction file generated next will henceforth be named {date in GMT}={Z}+{C}.zip, where Z is the randomId generated for the resulting transaction file. | ||
|
Owner
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This is a duplicate of the line just below. |
||
|
|
||
| Any transaction file generated next will henceforth be named `{date in GMT}={Z}+{C}.zip`, where `Z` is the `randomId` generated for the resulting transaction file. | ||
|
|
||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Were you able to confirm through experiment that is indeed the case?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes,
date in GMT of the oldest<date in GMT of the youngestORdate in GMT of the oldest>date in GMT of the youngesthas no effect on resulting file name