Yes, what I'm saying is that you should write and test this "engine" before even thinking of plugging the ORM into it. Mixing persistence and logic upfront is going to make it needlessly complex.
Write your entities, write their public API, code the logic and test it. After that start mapping associations. Marco Pivetta http://twitter.com/Ocramius http://ocramius.github.com/ On Tue, Oct 24, 2017 at 2:24 PM, OdaepO <oda...@gmail.com> wrote: > >I don't think this has anything to do with the ORM specifically > > sorry if I was not clear... > I was meaning what ORM's istruments/tools give to inherit an entity: > > example http://docs.doctrine-project.org/projects/doctrine-orm/en/ > latest/reference/inheritance-mapping.html > > ORM is about model... and I'd like to write the engine in model . > > However Sorry if this thread does not match very well with this group! > > Oda > > > > On 24/10/2017 14:02, Marco Pivetta wrote: > > 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 <oda...@gmail.com> 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 doctrine-user+unsubscr...@googlegroups.com. >> To post to this group, send email to doctrine-user@googlegroups.com. >> 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 doctrine-user+unsubscr...@googlegroups.com. > To post to this group, send email to doctrine-user@googlegroups.com. > 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 doctrine-user+unsubscr...@googlegroups.com. > To post to this group, send email to doctrine-user@googlegroups.com. > 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 doctrine-user+unsubscr...@googlegroups.com. To post to this group, send email to doctrine-user@googlegroups.com. Visit this group at https://groups.google.com/group/doctrine-user. For more options, visit https://groups.google.com/d/optout.
