webDEVILopers
webDEVILopers
Great feedback @yvoyer ... again. So looking at `Employee` and `Customer` from a different Context really changes the responsibility of the actor on the `Order` Domain Model? Indirectely the Customer...
And again we agree @yvoyer ! I will try to adapt what we talked about to my current project. There will be feedback by the Customer and the Developers at...
One question regarding your `getOffer` method: https://gist.github.com/yvoyer/c2c016b7fe5288554e3f6c432acafd65#L124-131 Though it is the Customer that indirectly confirms an Offer it is still the Employee who uploads an Order Confirmation and by this...
That brings me back to the beginning of this discussion. As I mentioned it isn't the Customer in person placing the Order. He calles the Office and the Employee enters...
Actually we do have something like a `SalesRepresentative`. The `Employee` belongs to the `Office`. Though `Office` simply extends `Employee` atm. And the `Office` will have to confirm the `Order` after...
Regarding your mapping suggestion @nidup: - https://github.com/akeneo/pim-community-dev/blob/master/src/Akeneo/Bundle/StorageUtilsBundle/Doctrine/MongoDBODM/Types/Entities.php I'm trying the other way around: `Order` Document has one `Customer` Entity. So I need an extra "Document(s)" Mapping type, right? Do you...
Thanks @nidup for this detailled answer! Looking at your mapping example: https://github.com/akeneo/pim-community-dev/blob/master/src/Pim/Bundle/CatalogBundle/Resources/config/model/doctrine/Product.mongodb.yml#L58-64 So you still have an "extra Field / Collection" to keep the IDs that have to be converted...
My current workaournd looks like this: I store my `Customer` via ORM (MySQL). `Orders` are stored in ODM (MongoDB). I have an `customer` property on my ODM Document. There is...
Thanks @jjanvier ! At the bottom line you are using an approach to the DoctrineExtensions by @Atlantic18: https://github.com/Atlantic18/DoctrineExtensions/blob/master/doc/references.md But you also support converting collections to Entities? Still you have an...
One final way to solve this and keep the `DomainModel` "clean" is to create a `DoctrineCustomer` Entity or `MongoOrder` Document that adds the extra field.