Morning Guys, On Jan 10, 5:49 am, "John Mettraux" <[EMAIL PROTECTED]> wrote: > So we have 3 possibilities > > a). attributes are stored in one column of the workitem table > b). attributes are stored in the field table (current implementation) > c). tree of attributes in the field table > > a). > + faster at read/write > - have to load all the workitems to query on fields > b). > - slower at read/write > + can do queries on top level attributes > c). > - super slow > + can do queries on attributes at all levels (except maybe on sub > fields whose keys are not strings) > > Is that it ?
For me, option b is best. It is very convenient to be able to query using the DB directly, and allows for better integration of the workflow with other applications. So I'm glad it sounds like both options will be there. My other thought is also this. When we add configuration options, it makes setup and learning and troubleshooting more complicated. So we should be thoughtful in adding options. It would be nice to see an actual use case for the change. It wasn't clear to me what use case going to yamalized versions for everything fixes. Is there something you can't do with the setup as it is now that you can do with the yamalized version? I want to understand that better. - August --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
