Automatically calculate average temperature and store the result.

a22erigr commented

2026-05-05 07:09:14 +00:00

Collaborator

Description

At the moment tempSensor generates alot of data. This will become problematic when we launch the application on the server. The obvious solution would be to delete old data. This unfortunately can't be done because we need old data to generate average temperature for year/month.

What should be done

After each day (00:00) all of the previous days data should be used to calculate average. The average should be places in a new table. AvrageTempDay. After this is done all of the previus days temp data should be removed.

## Description At the moment tempSensor generates alot of data. This will become problematic when we launch the application on the server. The obvious solution would be to delete old data. This unfortunately can't be done because we need old data to generate average temperature for year/month. ## What should be done After each day (00:00) all of the previous days data should be used to calculate average. The average should be places in a new table. **_AvrageTempDay_**. After this is done all of the previus days temp data should be removed.

a22erigr added the

help wanted

backEnd

SQL

labels

2026-05-05 07:09:14 +00:00

a24vinla was assigned by a22erigr

2026-05-05 08:42:23 +00:00

a22erigr removed the

help wanted

label

2026-05-05 08:42:28 +00:00

a24vinla commented

2026-05-05 09:00:34 +00:00

Collaborator

Do we want to keep the scheduling logic in the postgres DB (this would mean using pg_cron or similar) or in the application backend (asp.net extensions)? @a22erigr @c24danli

a24vinla added the

question

label

2026-05-05 09:00:44 +00:00

a22erigr commented

2026-05-05 09:10:49 +00:00

Author

Collaborator

Looking in to it

a22erigr referenced this issue

2026-05-05 09:36:31 +00:00

research if the scheduling logic should be placed in the database or in application backend #740

a24vinla referenced this issue

2026-05-05 11:56:47 +00:00

research if the scheduling logic should be placed in the database or in application backend #740

a24vinla commented

2026-05-07 13:38:45 +00:00

Collaborator

As per this comment we will use pg_cron to schedule database tasks

As per this [comment](https://git.webug.se/Andras/BoundlessFlowCampus2K/issues/740#issuecomment-8763) we will use pg_cron to schedule database tasks

a22erigr commented

2026-05-07 13:45:16 +00:00

Author

Collaborator

@a24vinla wrote in #727 (comment):

As per this comment we will use pg_cron to schedule database tasks
YES we should use g_cron.

@a24vinla wrote in https://git.webug.se/Andras/BoundlessFlowCampus2K/issues/727#issuecomment-8767: > As per this [comment](https://git.webug.se/Andras/BoundlessFlowCampus2K/issues/740#issuecomment-8763) we will use pg_cron to schedule database tasks YES we should use g_cron.

a24vinla referenced this issue

2026-05-08 07:58:40 +00:00

Adding pg_cron to Postgres Docker Image #834

a24vinla commented

2026-05-11 07:18:26 +00:00

Collaborator

I will change name of new table from AvrageTempDay to t_sensors_daily_average, if that is OK? @a22erigr @c24danli

a22erigr commented

2026-05-11 07:23:31 +00:00

Author

Collaborator

@a24vinla wrote in #727 (comment):

I will change name of new table from AvrageTempDay to t_sensors_daily_average, if that is OK? @a22erigr @c24danli

After a long and thorough discussion with the leadership we have decided that this decision is okay

@a24vinla wrote in https://git.webug.se/Andras/BoundlessFlowCampus2K/issues/727#issuecomment-9259: > I will change name of new table from AvrageTempDay to t_sensors_daily_average, if that is OK? @a22erigr @c24danli After a long and thorough discussion with the leadership we have decided that this decision is okay

a24vinla added reference 727-calculate-average-temperature-and-store-the-result

2026-05-11 13:55:44 +00:00

a24vinla added the

needs review

label

2026-05-11 13:55:52 +00:00