Yesterday, I had only made simple changes to the database tables (adding the new columns of "UnitPriceInCents," "RecipeRating"). This branch now includes changes in the code that reflects those additions to the table, such as:
-CreateIngredient and CreateRecipe methods now include their respective added fields
---Note: I have also gone into the references of these methods in the GUI and added the fields where necessary. Though, where the code to extract user text to create Ingredients is located I have only placed a default INT value so the one who will program the extraction of that info can have more control.
---Note2: For the CreateRecipe method, I followed Daniel's advice and placed a Nullable value that is also an optional parameter for the method. Hopefully this reduces the conflicts for the use of this method.
-Procedures referring to those methods have been changed
Now, I can more confidently say that we can work separately on Queries/GUI's based on the new Table Structure of our database. Though, if anyone finds any issues or has a bunch of conflicts when trying to merge, I can definitely take a look.
Again, sorry for the delay! Hopefully this doesn't cause a lot of conflicts with any work that has been done!
Sorry Everyone!!!!
Yesterday, I had only made simple changes to the database tables (adding the new columns of "UnitPriceInCents," "RecipeRating"). This branch now includes changes in the code that reflects those additions to the table, such as:
-CreateIngredient and CreateRecipe methods now include their respective added fields ---Note: I have also gone into the references of these methods in the GUI and added the fields where necessary. Though, where the code to extract user text to create Ingredients is located I have only placed a default INT value so the one who will program the extraction of that info can have more control. ---Note2: For the CreateRecipe method, I followed Daniel's advice and placed a Nullable value that is also an optional parameter for the method. Hopefully this reduces the conflicts for the use of this method.
-Procedures referring to those methods have been changed
Now, I can more confidently say that we can work separately on Queries/GUI's based on the new Table Structure of our database. Though, if anyone finds any issues or has a bunch of conflicts when trying to merge, I can definitely take a look.
Again, sorry for the delay! Hopefully this doesn't cause a lot of conflicts with any work that has been done!