Node properties are made multilingual

Node properties have been converted to support language variance on properties such as title. This is using the standard multilingual variance capability for properties that was introduced earlier.

• The {node} base table only holds
  | nid*| uuid | vid | type | tnid | translate |
  Primary key: nid
• The {node_revision} table only holds the revision metadata and language:
  | nid | uuid | vid* | revision_uid | log | revision_timestamp | langcode |
  Primary key: vid
• New {node_field_data} and {node_field_revision} tables are introduced for property data per language and for node revision property data per language.
  | nid* | vid* |type | langcode* | default_langcode | title| uid | status | created | changed | promote | sticky |
  • Primary key (node_field_data): nid + langcode
  • Primary key (node_field_revision): vid + langcode

For further details read Added multilingual support to the standard entity schema.

The main difference with the standard described above is that the bundle column (type) has been replicated in the {node_field_data} table to keep the related index and avoid a performance degradation for certain queries.