Hi Tom,
On Jan 10, 2008 8:36 PM, Tomaso Tosolini <[EMAIL PROTECTED]> wrote:
> Hi guys,
>
> in this days I'm procceding on an app that takes enormous advantage from
> OpenWFEru,
> and it's extension to enable db storage persistence, ...ooh... thanks to the
> one that wrote it!! :)
Yes, many thanks to you :)
> I was wondering if was reasonable a simplification of the workitems storage
> mechanism.
>
> (...)
>
> Why don't we remove completely the Field element and store (the yamlized
> version of ) wi.attributes directly into the workitems table???? It gets
> simpler to dump and load...
>
> Can I change this?
I agree with you entirely, but, there is a catch : it's not that bad
to have the fields in their own column, it allows for queries on them
like "return me all the workitems for which the field 'customer_name'
is set to 'Amerigo Vespucci'"...
But your use case makes sense as well. So why don't we decide at
initialization time how the ActiveParticipant should deal with its
workitems ? Maybe the current behaviour should be the default and your
more straightforward behaviour could be enabled via something like :
engine.register_participant "Amerigo", ActiveParticipant.new
:compact_workitems => true
and then this parameter (we should find a decent name for it), would
be passed to the Workitem instances each time a workitem is consumed /
proceeded by the participant.
Having an empty "field" table should not be a big deal.
What do you think ? Let's agree on something and then please do it.
Very good idea.
--
John Mettraux -///- http://jmettraux.openwfe.org
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"OpenWFEru dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/openwferu-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
