Hi there, I don't think this has anything to do with the ORM specifically: you should first design the interactions in your system, and leave the data requirements emerge from that.
Persistence/ORM comes after all that stuff is finished. Marco Pivetta http://twitter.com/Ocramius http://ocramius.github.com/ On Tue, Oct 24, 2017 at 11:55 AM, OdaepO <[email protected]> wrote: > I would like to write an engine for task management (workflow): > the engine manages tasks, states, people and groups and operations between > them. > This engine should be used by applications that specialize and customize > aspects of tasks (in a workflow). > > so I have a engine and (one or more) application wich **use** the engine... > > > the question is how can I (write and) use engine in the application? how > many way there are for doing that? > how can the application inherit behavior (functions, variables, > relationships) of engine's task? > how many ways do I inherit the task-engine from the task-application? > what is the best way to do that? > > thank you for your suggestions and warnings, > > Orda > > -- > You received this message because you are subscribed to the Google Groups > "doctrine-user" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/doctrine-user. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "doctrine-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/doctrine-user. For more options, visit https://groups.google.com/d/optout.
