in csns-create.sql we have "submissions" table which has the field "grade" , does adding rubric score substitute the "grade " or it is another form of extra grading field ?

1.are we allowed to have extra classes to implement Rubric itself (its properties) ?

2. there is a confusion on the class design , specially after going over the "RubricScoreDao" class .

----------List<RubricScore> getRubricScores( Assignment assignment, Rubric rubric );--------------

each assignment has a rubric associated , but the score does not get assigned to an assignment directly , so how we can get the rated score (given by the instructor for a given assignment to a student ) only by providing the assignment ?

1-is it possible for two different Rubrics to have the same kind of Criteria?

2- A rubric has a name, a rating scale which is either 1-3, or 1-4, or 1-5, and a number of criteria. , so there is no rubric allowed with 1 or 2 scale rate?

3. -for the purpose of doing the right approach and not have to redesign everything again -  I do not see any mention to submission table , should we get that involved ? or just use combination of student , assignment and Rubric for "RubricScore "

I am starting to run TestNG and I am running to some errors. in the powerpoint slides that we are going to cover for next lecture , we have some part for "Cascade"  . I had that cascade annotation in my class and the interesting thing was that after Maven process-clases nothing wa changed in the produced DDL file .?

because I am getting some errors for TestNG ,-that is saying it couldn't drop the table because other objects depend on it - I had to add some cascade keyword after the  the drop table name in my drop.sql  file , but here comes another question that might be more of sql type . suppose we have a couple of classes , our criteria class depends on the rubric class , so if there is no Rubric , then there would not be any criteria at all , so it totally make sense to drop all criteria tables dependent on the rubric table in a cascading manner.

but our rubric table relate to assignment class , they have relationship , sort of the same as the above (rubric and criteria), but it does not make sense to delete a rubric when we delete an assignment , although a rubric is linked to assignments , but it is a separate entity and cascading does not make sense here . but the problem / question is that what we should do , there is a constraint but we do not want to delete them , and TESTNG generate an error in this case that it is not able to drop the table because of dependancy?

TestNg fails two tests and skip the rest , and the other error that I have been getting so far is "illegal state exception:  it is failed to load application context ".  and it mentions the path  org.springframework.test.context.......

Thank you professor , just to clarify , I do not see any change in my DDl file , only in case of adding such a thing :

     @OneToMany(mappedBy=“owner”, cascade=CascadeType.ALL)

      List<Account> accounts;

otherwise it will change for other annotations . I guess Ill better wait till tomorrow till you cover this section and I will have more understanding of it .