MS Azure Storage Explorer
-
Sorting objects in blob containers in Storage Explorer is a joke. I have several thousand files in one container with Last Modified dates ranging from 6/3/2022 through 6/7/2022, and I need to delete all but those dated 6/7. I "sorted" them by the Last Modified date, ascending, and the first 100 cached items have dates of 6/3 and 6/4. I delete them, and after a few minutes the next 100 items are shown. There shouldn't be any more files from 6/3, but half of these are 6/3 files. I delete them, and rinse and repeat. Same date ranges, different files, dated 6/3 and 6/4. This tool is better than nothing, but not by much.
If you think 'goto' is evil, try writing an Assembly program without JMP.
-
Sorting objects in blob containers in Storage Explorer is a joke. I have several thousand files in one container with Last Modified dates ranging from 6/3/2022 through 6/7/2022, and I need to delete all but those dated 6/7. I "sorted" them by the Last Modified date, ascending, and the first 100 cached items have dates of 6/3 and 6/4. I delete them, and after a few minutes the next 100 items are shown. There shouldn't be any more files from 6/3, but half of these are 6/3 files. I delete them, and rinse and repeat. Same date ranges, different files, dated 6/3 and 6/4. This tool is better than nothing, but not by much.
If you think 'goto' is evil, try writing an Assembly program without JMP.
This sounds like it is similar to a problem I encountered with Oracle some years ago (10+ years?). In the previous version of Oracle (7 or 8?), a statement like (my Oracle SQL syntax is rusty, so this may be incorrect)
SELECT TOP 1000 Surname
FROM Employees
ORDER BY Surnamegave an alphabetical list of 1000 surnames starting at A and going as far as (say) C; but the next version (10?) gave an alphabetical list of 1000 surnames not necessarily starting with A and not necessarily ending with C. I spotted it, because my name used to appear in the answer, but then stopped appearing. The reason (I worked out) was that the old version did the ORDER BY first, then the TOP 1000 (so they were pre-sorted then truncated); and the new version did the TOP 1000 first, then did the ORDER BY (so they were sorted after truncation meaning that you got a random sample). Both are - as I understand it - valid results from the SQL statement, but the difference upset a lot of people (including myself) who thought that they had been eliminated and not told about it. My solution, to get my preferred old-style list, was something like (again, my Oracle SQL is rusty)
SELECT TOP 1000 Surname
FROM
(
SELECT Surname
FROM Employees
ORDER BY Surname
)I don't think that your description fits that scenario; but could the caching have unsorted the data? Bad design if that is what had happened.
-
Sorting objects in blob containers in Storage Explorer is a joke. I have several thousand files in one container with Last Modified dates ranging from 6/3/2022 through 6/7/2022, and I need to delete all but those dated 6/7. I "sorted" them by the Last Modified date, ascending, and the first 100 cached items have dates of 6/3 and 6/4. I delete them, and after a few minutes the next 100 items are shown. There shouldn't be any more files from 6/3, but half of these are 6/3 files. I delete them, and rinse and repeat. Same date ranges, different files, dated 6/3 and 6/4. This tool is better than nothing, but not by much.
If you think 'goto' is evil, try writing an Assembly program without JMP.
Yeah, working with blobs like that is a drag. I don't really work with blobs outside of my code anymore. I can delete all or a few manually, but for that kind of work I write a quick console application that does the work for me :~ Luckily I rarely do that kind of stuff, it's mostly a few :)
Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript
