[TYPO3-mvc] non-db based value objects and embedded values - how to?
Martin Kutschker
masi-no at spam-typo3.org
Thu Jun 10 21:37:52 CEST 2010
Jochen Rau schrieb:
> Hi Masi.
>
> On 2010-06-10, Martin Kutschker <masi-no at spam-typo3.org> wrote:
>>>> Or how to extend the data mapper? As I perceive it the data mapper is currently limited to scalars
>>>> and object relations. Even value objects are treated as relations in as much as Extbase supports
>>>> AFAIK only value objects which values are based on a DB table.
>>> Do I miss the obvious and what I am asking for is already there? Or do I want something that you
>>> don't think is necessary?
>> Jochen, Sebastian, could you please tell me if I am wrong? If I'm not please direct me if I should
>> simply file a bug or if I have pick up my pattern books and look for a solution that fits into Extbase.
>
> Sorry for being absent the last couple of days. We had to prepare our move to Amherst (Mass.).
>
> FLOW3 has the concept of custom factories that fits your needs imo.
>
> http://flow3.typo3.org/documentation/manuals/flow3/flow3.objectframework/#id37778491
While I agree that they are nice, they are not what we need. Our problem is that there is only one
data mapper and that it cannot be augmented. The issue is that it know only a very limited set of
data types (PHP scalars, referenced/persisted TCA objects and DateTime). So we want either hhave a
way to add more types in general or to add more types on a per class/model/table base.
Masi
More information about the TYPO3-project-typo3v4mvc
mailing list