Closed (won't fix)
Project:
Drupal core
Version:
8.0.x-dev
Component:
system.module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
24 Mar 2012 at 19:48 UTC
Updated:
1 Oct 2014 at 13:18 UTC
Jump to comment: Most recent, Most recent file
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 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.