As long as you define your inline fields outside of a list/task context, they’re all gobbled up into a list, and you’re making it harder for yourself to query on parts of that list of dates.
Using your example, we could do these quiries:
## Original field single/list
```dataview
TABLE 🎁, flat(list(🎁))
WHERE file.folder = this.file.folder
```
## FLATTEN the values
```dataview
TABLE aDate
FLATTEN flat(list(🎁)) as aDate
WHERE file.folder = this.file.folder
```
Which renders as follows with your two test files:
Notice how in the first query second column that the file with multiple dates list them as a list, while the single value is just a single value. This causes hammock when trying to compare against anything as the former needs to use contains() & co, and the latter needs to use the equality operator. This can however be countered by forcing everything into a list, using the flat(list( ... )) trickery. See third column for the result of this trickery. Now we can use contains() against any variant single or list. 
Also note in the first query how all the dates are bungled together and displayed as one row. In the second query we flatten the list into single items, and get a table with four rows. Now we can only also limit the result to any of those dates.
However, in neither of these queries are you able to associate the text of “Birthday” or “Date one” and so on to the actual date itself…
Using lists
If on the other hand you used definitions like:
First note:
- (dateType:: Birthday) [💝:: 07.11.2023]
- (dateType:: Date one) [💝:: 10.10.2023]
- (dateType:: Date two) [💝:: 11.10.2023]
Second note:
- (dateType: Birthday) [💝:: 07.11.2023]
We could a query like the following:
```dataview
TABLE item.dateType, item.💝
FLATTEN file.lists as item
WHERE item.dateType
```
And get the result:
Finally, we’re getting somewhere close to checking a single date against something. There is just one hurdle left to pass, and that is that “07.11.2023” isn’t recognised as a date directly by dataview. So either you need to format the date of the daily note into that format using dateformat(...), or we need to make the field into a date using something like date(item.💝, "dd.MM.yyyy")
Using the latter we could do a query like:
```dataview
TABLE item.dateType, item.💝, date(item.💝, "dd.MM.yyyy")
FLATTEN file.lists as item
WHERE item.dateType
AND date(item.💝, "dd.MM.yyyy") = date("2023-11-07")
```
Still using the same test data this displays the following table:
Where you could replace the last date("2023-11-07") with file.day given that your daily note has a properly set date (or use the same date conversion as suggested for item.💝).
PS! Using file.cday is not a reliable way to check for the creation date, as it might be changed during various file synchronisation issues, backup/restore issues and so on. You’re better of either setting the creation date using date: ... or by including the ISO-date into the file name itself. Then you can access this date using file.day.
” field coincides with the date of the note.
