Based on #1498634: [meta] Define revision/translation SQL schema for core entities (no patch) there should be a new schema. The name should be file_managed_translation it's connected to file_managed directly.

#2 1498668-file-translation-schema.patch811 bytesdawehner
PASSED: [[SimpleTest]]: [MySQL] 35,913 pass(es). View
Members fund testing for the Drupal project. Drupal Association Learn more


dawehner’s picture

Issue tags: +D8MI, +language-content

Add tags

dawehner’s picture

Status: Active » Needs review
811 bytes
PASSED: [[SimpleTest]]: [MySQL] 35,913 pass(es). View

Here is a first patch. I wasn't able to find a column which wouldn't make sense to be translatable.

Gábor Hojtsy’s picture

Status: Needs review » Needs work

Update functions should clearly not use dynamic schema information. If this update function is used later, it would create a different schema. We have a practice of hardwiring all information needed for an update function to ensure it does the same thing regardless of time it ran.

Gábor Hojtsy’s picture

Issue tags: +sprint

Also mark for the sprint board.

Gábor Hojtsy’s picture

Issue tags: -sprint

Moving this off sprint since looks like #1498634: [meta] Define revision/translation SQL schema for core entities (no patch) needs some more discussion in regards to revisions.

Gábor Hojtsy’s picture

Title: Define file translation schema » Refactor file entity properties to multilingual
Tor Arne Thune’s picture

Status: Needs work » Postponed
mgifford’s picture

plach’s picture

Status: Needs work » Closed (won't fix)

The (core) file entity is not translatable, so no need to change its default schema.