Scheduler + Views: add field handlers for task parameters

#1: 1319538-1-field_handlers_for_parameters.patch queued for re-testing.

interesting approach. I'm not sure about going this way though. First off, it's really not the usual way Views works. Second, once we go that route people 'll want relationships and stuff like that. So let's better not open that can of worms....

Maybe though, I'd be a good idea to work upon an improved storage for that data. I.e. have a table that has entries like 'data_type', 'value'. That should even make relationships possible + should be much easier to port to future rules versions as there are no special classes serialized...

Note that a bit problematic are data structures being no entities and having no id - we'd still have to store them serialized.

I wonder what klausi thinks about that idea.

Fago and I talked about this: to do a proper Views support we should move the parameters of scheduled tasks to a separate table (e.g. rules_scheduler_param). We should focus on entity parameters as they are most likely a use case here (e.g. list all scheduled tasks for a node, for a user etc.). So the colums of such a table would be:

task id
param name
param type
entity id (integer, only set if the param type is an entity)
param value (serialized, only set if the param type is not an entity)

We use 2 columns for the value here because we want to index the entity id column for fast access for our actual use case. Another advantage of this approach is that we do not have serialized entity wrapper classes in the DB anymore, which eases the upgrade path to Drupal 8 where the wrappers will not exist anymore.

Unassigning myself as I currently don't have time to work on this ... Itangalo do you want to take a stab at this?

Had a need for this myself, and implemented part of #6. Had to do it very quickly, so the parameters are still serialized in the rules_scheduler table, but now there is also a rules_scheduler_params table which is exposed to views. Relationships are also still to do, but this lays the groundwork, I think, and includes sort/filter handlers.

I'm trying to use your patch for the Learn the Rules framework screencast ( Which is great!) but I'm having problems setting up the view for scheduling front page content. When I try to add the Rules parameter: Node (node)
Data from the parameter called Node (of type node), used in component rules_publish_on_front_page. - to my table I get a missing handler error.

Any ideas?

Thanks
Sharon

ok -
It was worth as shot, Thanks anyway!

Sharon

I have spent some time upgrading this patch, expending on the relationship side.
I have also registered rules scheduler task as an entity in order to use it with VBO (Views Bulk Operations)
I did my best by please review thoroughly

Corrected patch for incorrect filepath...

Last try, hope it is the good one
With apologies for those who follow this issue and have polluted mailbox because of me...

Moving to 8.x-3.x.