To ensure that we are not storing an average score every time the function runs, we need to have a unique identifier for the average. For AverageDocumentScore table, we chose the date as the unique property. Thus, only a single average score will be stored for each day, and this score will be updated if the function re-runs.
To ensure that we are not storing duplicates, we need to find the entity (SQL table row) if it already exists. Loading all the data stored in the AverageDocumentScore table and then searching for existing entities on a particular date can become a very "costly" operation as the table grows. To avoid doing that, we are going to use the query parameter of the ListEntitiesAsync() method, which ...
