Rather than keeping a count on UserCocktail, which gets erased if a user removes the cocktail from their list, a new table in the database should store an entry for each cocktail a user makes, with a timestamp. If a user makes multiples of a cocktail, store a new entry for each instance.
Rather than keeping a count on UserCocktail, which gets erased if a user removes the cocktail from their list, a new table in the database should store an entry for each cocktail a user makes, with a timestamp. If a user makes multiples of a cocktail, store a new entry for each instance.