Open dcolli23 opened 4 years ago
I should probably take a crack at learning some form of SQL for this.
Well I think the time has come for me to start addressing this. I believe that I should look at NoSQL databases for this since I'll probably want to store recipes as objects instead of regular tables of information like in SQL databases.
Description
I need to consider managing a database for "caching" previously looked up ingredient information. That way, I can cut down on the amount of GET requests I make with the bar code API, potentially mitigating the need to buy any subscription to it.
I could also think about doing this for recipes.