Chris Howe wrote:
The following appear as if they could be reintroduced as orderTypes with additional tables for their unique fields order.request order.quote order.return
In general, I'm against this kind of refactorings: there are definitely pros and cons for the two approaches and we could definitely discuss about them for days and days (probably without any agreement on the best solution); so I am pragmatic on this: there is a lot of existing code built on top of these entities, no specific problems caused by this design -> thus no reason to change; especially if the change is suggested by the bare analysis of the data model and not also on the existing business logic and existing problems that the data model is causing.
So, no I'm against this change. Jacopo
