- 🇺🇸United States smustgrave
This something we want to include in a last few D7 releases?
- 🇺🇸United States smustgrave
Since there hasn't been a follow up from anyone still on D7 going to say this can be closed as outdated. Thanks!
I was trying to do #2378359: Convert Questions to D7 Entity API → when I noticed that we have redundant data storage and cannot correctly make Quiz questions entities. Any efforts would just be heading in the wrong direction.
Now that quiz "questions" {quiz_question_properties table} are considered an entity internally let's make the built in question types relate to them only on the question ID instead of nid/vid. We gain a couple things from this including Entity definitions and Views support now that they will relate on 1 field. Having redundant primary keys is also bad practice.
This also will take the versioning responsibility off of the question and question types as it will allow us to take advantage of EntityAPIControllerRevisionableInterface later.
For example
quiz_question_properties ("question" table)
- nid
- vid
- qqp_id
quiz_truefalse_node
- nid
- vid
(should be:)
quiz_truefalse_node
- qqp_id
This helps with #2378359: Convert Questions to D7 Entity API → , as when using entity API/Views we prefer single non-redundant keys on tables when linking to another table.
- Migrate question types schema nid/vid to qqp_id
- Update entity reference definitions so that questions types relate back to the qqp table.
- Change "saveNodeProperties" to just "saveProperties" as we are not saving nid/vid anymore.
None
Schema fields (not yet accessible to Views) change.
Postponed: needs info
5.0
Code - Quiz core
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
This something we want to include in a last few D7 releases?
Since there hasn't been a follow up from anyone still on D7 going to say this can be closed as outdated. Thanks!