- [x] **[PS]** refactor relationships for plural/singular relation names - [ ] **[PS]** update all instances of validation to use new `Validation.pm` - [ ] use `->insert` wherever `->new(...)` is used for row creation - [x] ~~add `fetch_with_defaults` as an alias for `discard_changes` and employ everywhere `add_to_$rel` is used~~ - [x] **[PS]** eliminate dependency on `List::MoreUtils` (~~firstval~~) - [ ] **[AP]** update all `$self` to use more appropriate naming convention - [ ] **[GR]** switch tests in `t/db` to use `Test2::V0` - [ ] **[AP]** Instead of throwing errors on fields not in the DB, filter out non-existent fields. This is done in `ResultSet::UserSet::addUserSet` - [x] **[PS]** DeleteXXXX in ResultSet classes should return `200 OK` and the tests should check to make sure that the XXX was deleted. - [ ] resolve UserProblem `problem_version` (nullable _with_ default value?) add uniqueness on user+problem+version - [ ] Attempt field `comments` is a JSON column? - [ ] Include a created_date and updated_date field in each table - [ ] Uniformize test checking of boolean fields (and update DB to ensure proper booleans on create/update/fetch)
Validation.pm->insertwherever->new(...)is used for row creationaddfetch_with_defaultsas an alias fordiscard_changesand employ everywhereadd_to_$relis usedList::MoreUtils(firstval)$selfto use more appropriate naming conventiont/dbto useTest2::V0ResultSet::UserSet::addUserSet200 OKand the tests should check to make sure that the XXX was deleted.problem_version(nullable with default value?) add uniqueness on user+problem+versioncommentsis a JSON column?