[TYPO3-ect] domainLayer for lib/div?

[Steve Ryan]

I did some research into comparing PHP object persistence frameworks.
http://wiki.typo3.org/index.php/Object_Persistence_Framework
put together the start of an active record style extension to lib object
http://svn.syntithenai.com/svn/t3ext/persistence/

I think the bottom line for any object persistence framework is the
balance between relationship support and simplicity.
Access to raw SQL will always be required.

Steve









Elmar Hinz wrote:
>> I my last self developed framework I integrated a so called
>> "domainLayer". And I just want to ask, if it is interesting for lib/div?
>>
>> A domain-object represents a real-life object like a user, article,
>> banana ...
>>
>> Each domain-object provides methods to automatically retrieves and saves
>> itself to the database:
> 
> Hello,
> 
> here we come to the topic of ORM. That is very important, but can be
> seperated from the MVC architecture. In this table you see that several
> python frameworks use SQLAlchemy. 
> 
> http://en.wikipedia.org/wiki/Comparison_of_web_application_frameworks
> 
> I think that we also should seperate this from lib. So we can have
> flexibility and competition to find the best architecture. I have no own 
> experiences with ORM, so this is a good fild for others to hook in.
> 
> We definitly need a taskforce to come to solution(s) here. Maybe you could
> ship your files as an add-on for lib as a first option. 
> 
> On the long run we need "full power solutions", that can compety with the
> rich features and popularity of SQLAlchemy or Rails Clones.
> 
> There are different beginnings:
> 
>  * your proposal
>  * the TCAObjects of WEC
>  * the suggestion of Philip Almeida a few days ago
> 
> Regards
> 
> Elmar
> 
> 
> 
> 
> 
> 
> 
>