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!! :)

I'was wondering if was reasonable a simplification of the workitems storage
machanism.

Well,
take a workitem, it has the attributes hash where we can find it's fields.

when stored ( extras/participants/activep..rb line 170 more or less ) in
Workitem.from_owfe_workitem
 it happens

...
wi.attributes.each - create an object Field and save in a different
table.....


ok but now suppose you have a similar situation

wi.attributes = {
    :x1 => v1,
    :x2 => v2,
    :x3 => {
       :x31 => v31,
       :x32 => v3
    }
}

once saved you have:

a record in workitems ok this is good

three records in fields!!
1: name = x1, svalue = v1
2: name = x2, svalue = v2
3: name = x3, svalue = yaml of { :x31 => v31, :x32 => v3 }


i think that this is useless, because everytime wi_fields are a little
structured, Field records will have always yamlized values
and so:

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?


( soon i'll reply about stable release... ;) )


Bye
Tom

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to