Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.These columns are defined by hook_schema but not in hook_views_data for node_field_revision:
- langcode
- default_langcode (I don't think this is necessary)
- revision_timestamp
- created
- comment (I don't think this is necessary)
- promote
- sticky
Not sure if all this columns need to be stored in this table, things like created, comment, promote, sticky seem a little redundant?
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | 2032977-missing_node_field_revision-2.patch | 2.92 KB | pcambra |
| #1 | 2032977-missing_node_field_revision.patch | 2.6 KB | pcambra |
Comments
Comment #1
pcambraComment #2
pcambraAdded revision timestamp
Comment #3
dawehnerI guess we want to have some basic tests in order to know that it works in the future.
The actual missing fields (coming probably from the node_revision => node_field_revision page). look fine.
The question is whether we want to support a filter for the langcode if the language module is disabled (a basic string one).
Comment #4
PanchoDoesn't block #1863906: [PP-1] Replace content revision table with a view, so I'm tentatively postponing this to the critical #1998366: [meta] SQLite is broken, which will soon introduce changes to the whole schema. Marking it major + tagging it, though.
Comment #4.0
Panchorevision timestamp <> created
Comment #5
MustangGB CreditAttribution: MustangGB commentedLooks like any schema changes are done now.
Comment #6
catchNot sure why this needs to be tied to the release schedule given it's not critical.
Comment #7
xjmComment #8
dawehnerWe do have those now added automatically, yeah!