For a project I had the idea to use node revisions for monthly reporting to make it easy to automate some stuff with rules. So what I've done now is created a pivot table of the node revisions like this:

**********REVISION DATE 1********** REVISION DATE 2********* REVISION DATE 3*******
--------------------------------------------------------------------------------------------------
node 1 | field_revision_1.1 | field_revision_1.2 | field_revision_1.3 |
--------------------------------------------------------------------------------------------------
node 2 | field_revision_2.1 | field_revision_2.2 | field_revision_2.3 |
--------------------------------------------------------------------------------------------------

I hoped I could use editable fields in this view to change the data but EF show the data of the published version instead of the data of the revision. When I change the data it changes the published data...

I've seen some issues on EF support for revisions (which would be great too) but what I need is the possibility to change the fields of a revision (and this without creating a new revision).

For my view I'm using the "content revisions" type so I guess it could be possible for EF to detect whether the field that's going to be edited is comes from the "field_data_[fieldname]" table or the "field_revision_[fieldname]" table. Is this logic correct or not and does any of you know how to solve my problem (other solutions also welcome)...