This is trickier than one should aspect mainly due to three reasons:
When using LIST it doesn’t recognise created-date, but needs to use row["created-date"] due to that dash, or minus sign, indicating that you’re actually trying to subtract date from created in the first variant.
Your current format is not actually a date, it’s just a string. To make it a legal date you need to do 2023-01-28T08:40
And even if it was recognised as a date, then a date with a timestamp is not necessarily equal to a date (without that timestamp). That is, 2023-01-28T08:40 is not equal to 2023-01-28.
So how to compensate against all of these reasons?
With no changes in your base data
With no changes in your base data you’ll need something like this monstrosity:
WHERE dateformat(date(substring(string(row["created-date"]), 0, 10)), "yyyy-MM-dd") =
dateformat(date(substring(this["created-date"], 0, 10)), "yyyy-MM-dd")
I wouldn’t go there… This is a beast…
With changes in your base data
I would strongly recommend two changes:
First of all change into proper dates by adding that T into the string, like in 2023-01-28T08:40 (or simpler, just remove the timestamp, and just leave 2023-01-28)
Change from created-date into created_date, which doesn’t need all that special care through using row["created-date"] to access it
If you do both of these, you’ll end up almost with what you started with:
WHERE created_date = this.created_date
Or if you don’t want to loose the timestamp
This depends on whether you’ve got the timestamp included in all files, or just this file. If in all files, you’ll need to also change the part related to created_date accordingly to the this.created_date.
FROM created_date = dateformat(this.created_date, "YYYY-MM-DD")
So there you have it, changes need to be made, if you want to avoid the monstrosity in the beginning. Which changes kind of depends on how many notes we’re talking about, and which format you’ve already got for the created-date in those notes.