The field_data_myfield and field_revision_myfield have the same row entries (D7 fields). All of my content types have the "Create new revision" unchecked. Is this how it's suppose to work? If yes, two questions 1) is this okay for scalability and 2) how do I stop drupal from renaming the files with _0 even when the original is deleted -- I read that this is because revision is on. If it's not suppose to work this way, how do I fix it.

I'm using mysql.

To clarify the end goal, I don't want the entire field deleted, I would like the fields not to track data revisions. Currently if field_body is updated, it also tracks it in field_revision body. Ideally, drupal would only save the update in field_body, and field_revision_body would be left empty. The content type is marked to not track revisions.

  • Even with revisions turned on, if you delete a file that is not used on any other revision the file will be removed. Since you are not using revisions there will be only one revision, which means when you delete a file the file should be deleted from the server and you should avoid the numeric suffixes on the file names.
    – rooby
    May 11, 2013 at 8:39

1 Answer 1


Is this how it's suppose to work?

It depends on which storage backend you use. The default sql backend works this way.

  1. It shouldn't effect speed (much) but will instead effect data storage which usually isn't a problem.
  2. Drupal will not completely delete a field, but instead mark it as deleted. If you want to completely delete it, you need to delete it from the field_config and field_config_instance tables.
  • Hello Googletorp, would it be safe to trunace the revision field? It does not seem it is used at all since revisioning is turned off.
    – giorgio79
    Dec 12, 2011 at 13:08
  • @googletorp see also the drupal.org/project/field_sql_norevisions module ... its an all or nothing module that disables revision tables for your content types.
    – tenken
    Apr 7, 2013 at 2:53

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.