ibeal
commented
3 years ago This problem has been double fixed. I applied the original fix (to filter out chars on entry and add them back in upon retrieval), however the new direction to adding list support to the database, has made this issue obsolete, and only used for backwards compatability
I need to replace all apostrophes and parenthesis with bogus characters in the db, otherwise I get weird issues. Only the list-string datatypes have issues with so far, but all the string fields could potentially have issues.
I will delegate responsibilities to the recipeAPI class to make sure that these characters are filtered out when going into the database, and they are replaced when leaving the database. The RecipeAPI will apply the filter when asked to save a recipe, and will apply the filler when asked for a recipe or recipes. The filter and filler functions will, however, live in the database class, as static methods. This is in case the other APIs need access to the functions.
[x] filter out characters on db entry
[x] fill back in on db exit