It's great that the counting of brewing sessions has been fixed in the latest release!
I sometimes use the "brew" button in order to see the mash water calculator and figure out the amounts I want to put on my mash steps. This has been distorting the brew counts of my recipes, because deleting the sessions didn't decrease the brew count. now it works great.
*But*, it would be nice to do "refresh" in the database now and reset all the brew counts according to the number existing brew sessions, so that the recipes that are already skewed (like my own) would get fixed.
Actually, maybe instead of having a field where the brew counts are recorded in the recipe it could be counted dynamically each time the value is requested? Something like: "brewcount = count brewsessions where brewsession.recipe_id == requested_recipe_id". Would that be too heavy to do each time at runtime?
I sometimes use the "brew" button in order to see the mash water calculator and figure out the amounts I want to put on my mash steps. This has been distorting the brew counts of my recipes, because deleting the sessions didn't decrease the brew count. now it works great.
*But*, it would be nice to do "refresh" in the database now and reset all the brew counts according to the number existing brew sessions, so that the recipes that are already skewed (like my own) would get fixed.
Actually, maybe instead of having a field where the brew counts are recorded in the recipe it could be counted dynamically each time the value is requested? Something like: "brewcount = count brewsessions where brewsession.recipe_id == requested_recipe_id". Would that be too heavy to do each time at runtime?