[Flow] Storing Generic Objects

[Carsten Bleicker]

think the most travis failures produced by models using fixtures with injected properties.
after the first failure the persistence is closed so any following test also fails.
my tests are successfull if i add also @Flow\Transient to these properties.
should not be @Flow\Inject always also mean "its transient too automatically"?



Am 25.03.2014 um 16:27 schrieb Carsten Bleicker <carsten at bleicker.de>:

> hi,
> to store the orders in my shop i want do build up simple order objects implementing \Serializable interface.
> i want this to be stored in the db as serialized objects containing several infos. delivery, product title, price of product
> at the moment i send the order etc etc. so i have my order object wich is NOT an entity or valueobject. Its just a simple Object
> wich supports serialize interface. but flow seems only be able to handle its entities and valueobject. Using extended stuff of doctrine
> is not possible i think. f.e. this one: 
> http://docs.doctrine-project.org/projects/doctrine-dbal/en/latest/reference/types.html#custom-mapping-types
> 
> my patch is just a first idea i want to discuss. its not final etc. but flows persistence layer is imho a bottleneck wich does not allow me to use doctrines power.
> many doctrine features seems to be not possible. another example: \DateInterval storing to db not possible.
> 
> the idea i want to discuss is this:
> https://review.typo3.org/#/c/25907/
> 
> my goal:
> https://gist.github.com/pumatertion/9763893
> 
> Problems:
> 1. Properties containing an Object withoud XtoY Relation annotation seems not to be in the reflection.
> So not generated in the db by doctrine:update
> 2. FlowAnnotationDriver does not respect object and its type configuration so doctrines custom mapping types never possible i think
> 
> 
> kind regards
> carsten
> 
> 
> _______________________________________________
> Flow mailing list
> Flow at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/flow