Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
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.
Comment | File | Size | Author |
---|---|---|---|
#2 | 1498668-file-translation-schema.patch | 811 bytes | dawehner |
Comments
Comment #1
dawehnerAdd tags
Comment #2
dawehnerHere is a first patch. I wasn't able to find a column which wouldn't make sense to be translatable.
Comment #3
Gábor HojtsyUpdate 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.
Comment #4
Gábor HojtsyAlso mark for the sprint board.
Comment #5
Gábor HojtsyMoving 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.
Comment #6
Gábor HojtsyRetitle based on #1658712: Refactor test_entity schema to be multilingual. Marking postponed on #1691952: Make EntityFieldQuery work with multilingual properties.
Comment #7
Tor Arne Thune CreditAttribution: Tor Arne Thune commentedComment #8
mgifford#1691952: Make EntityFieldQuery work with multilingual properties is fixed.
Comment #9
plachThe (core) file entity is not translatable, so no need to change its default schema.