[TYPO3-ect] New roadmap lib/div/cool

[Michael Knoll]

Hi again,

I forgot a link, I referenced in my last post, so here it is:

[1] http://www.martinfowler.com/eaaCatalog/


Some additional things are below in the text.

Good night everybody

Michael





Elmar Hinz schrieb:
> Michael Knoll wrote:
>  
>>> 2.) Making a tca2xml converter for propel configuration.
>> As you can use "reverse engineering" from your DB structure to Propel
>> XML, perhaps that's rather the way to go than creating XML out of the
>> TCA structure - but I will give it a try!
> 
> Oh, if all informations can be extracted from the DB there is no need to use
> the TCA. I just thought some additional informations would be required. If
> not it's even more easy.
> 
>  
>> Still there are some points, I forgot in my last post, where we have to
>> find a solution
>>
>>
>> 1) Double DB Access with Propel:
>> ================================
>>
>> Propel doesn't use T3 DBAL and replaces it with Creole.
>>
> 
> That is a difficult point. It requieres some care to keep the DB model
> intact, the timestamps, the user ids etc. Good documentation is of help
> here. It's outside the coding standards and only good research and
> documentation can show, that is equivalent. But I think it's worth the
> investigation.
> 

I will try to "extend" the Propel classes for automatically setting 
those fields in the database. Didn't think about that yet!

> 
>> 2) Fake M:N relations:
>> ======================
>>
>> Propel won't be able to work with these non-atomar database fields.
>> Besides they
>> are really messy, the developer will have to extend the basic Propel
>> classes, so
>> that they can do the job. I will put this in my documentation.
> 
> Developers should avoid "non-atomar" database fields. It's possible to work
> with TYPO3 in a clean way, at least when setting up new tables. It's
> possible, it should be the standard.

But there are many of those "non-atomar" database-fields in the "core" 
tables, that don't come with extensions. I think, we have to cope with 
those fields at least.

> 
>>
>> I will use the weekend to put that all together in a first draft for a
>> documentation extension and send you a link to read it!
>>
>> Thanks for sharing your ideas, I hope, we get this working!
> 
> Yes that would be very nice. It seems the bigger part is already done.
> 
> Regards
> 
> Elmar
> 
> 
> 
> 
>