On Thu, Dec 29, 2011 at 4:48 AM, herman vierendeels <[email protected]> wrote: > Should we not merge company/entity ? > Remove entity_class on that level and only define it on lower level? > > In that way, company/entity could represent > customer,vendor,employee,myOwnCompany,other_business_relation
Actually I want to be able to make it so that persons can also be customers/vendors. This means moving some things from mapping against company and person to mapping against entity. So some refactoring needs to take place but I am not sure I want to see entity and company get fully merged since we need some sort of stub to hang connections on between these. Also the sorts of mappings our database schema allows goes *way* beyond what we are currently using. Part of the reason here is to encourage third party development on CRM areas. Best Wishes, Chris Travers ------------------------------------------------------------------------------ Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox _______________________________________________ Ledger-smb-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ledger-smb-devel
