The major issue is that you stored your dates in the format
With this format you cannot compared 2 dates and determine directly if one is before the other. You need to convert the stored date into the ISO format before you are able to compare, sort, … That will be slow since you will compare on a computed field.
The only smart thing to do is to migrate your data to ISO date.
I think you’re out of luck using that date_time field as stevej pointed out, it’s in a horrible format for any date comparrison.
Going forward I think the best option would be to convert them all to dates and store it as an actual date going forward. This will be searchable and also require less space for storage.
An alternative may be to use the object id, this has the date time embedded within it, so assuming you’re just pushing data into the server without doing anything funky with the objectIds (i.e. letting the driver or server generate them as opposed to hand crafting them) you could find the document ID that was created on that date, and get anything with an ID higher.
Your date format is so bad for your use case that you cannot save time.
You have 2 choices
1 - permanently convert and migrate your data to an appropriate date format and waste time once for the migration
2 - dynamically convert your data to an appropriate date format and waste time every time you query your data
WHY because your date format does not have a natural chronological order so there is not way to say find date_time greater than 8th august 2023. Because in your date format 9th august 2022 is greater than 8th august 2023.