Week 5 ready for review

[misterToo]

@pawaitemadisoncollege Key learning points: Stack traces contain more than I thought they did, was able to solve my problem with a little help

Challenges: One to many annotation/SQL with hibernate is a little "black box"-y if that makes any sense, don't quite understand how it works.

Problems solved: getting all the column names correct for hibernate to work with my table, solved with the help channel in slack, needed a little pointing in the right direction

[pawaitemadisoncollege]

@misterToo Yes! Hibernate/JPA takes some practice to fully understand! It does feel like magic sometimes when a framework writes sql for you. The key thing to remember is that you control that with annotations and the database set up.

• [ ] Unit tests do not verify the relationships are working. Example: a user with one or more orders.
• [ ] Update scenario is not accounted for in the tests.
• [ ] Delete scenarios should be more fully tested by checking what happens on the other side of the relationship when an entity is deleted. For example, if you delete a user what should happen to their orders? What if you delete an order? Write tests to make sure what should happen does happen.
• [ ] You'll likely notice, if you haven't already, that writing a Dao for each entity will be very repetitive - watch for the abstract/generic dao to be introduced in the coming week and plan to use it in your project so that you can use a single dao! Note that you will still have unit tests each for each entity(dao) to make sure that annotations and database relationships are set up correctly.