Thanks, I was hoping for more friendly syntax. Dan, this is only an example, I'm not talking about implementing workflows but about using db-level consts. There are many (about 30) such dictionaries in my application, representing statuses, types, subtypes, categories and other auxiliary lists, only few of them are workflow-related. I think I'll do as Diego says and will not map these tables to NH, using integer enums instead.
RG On 14 Gru, 10:38, Dan B <[email protected]> wrote: > +1 for this: > > > A cleaner approach (if you're comfortable with it) is to use the Id as a > > discriminator and use WorkflowStatus for a State/Strategy pattern. > > It works well for simple linear workflows. -- You received this message because you are subscribed to the Google Groups "nhusers" 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/nhusers?hl=en.
