[FLOW3-general] Diffrent packages with simillar models + Doctrine

[Dawid Pacholczyk]

I agree that using 2x Blog packages is wrong BUT (there is always a 
"but") what if I created my own Blog package and my friend sends to me 
his implementations from which I want to take 1 or 2 classes (well come 
packages where invented for that :) ).

Only exit from this problem is to use @table but changing someones else 
Package might bring more problems. This should be configurable from some 
level...for example mapping Model on some othere name in my DB. It would 
be like xclass in TYPO3 v4 ( hmm ? ). You change 1 line but don`t change 
anything in the original code.

What do you think ?

Best regards.
Dawid "Fixus" Pacholczyk

On 23.03.2011 18:32, Andreas Förthner wrote:
> Hi,
>
>> What to do? Is it reasonable to assume one would not use two different
>> Blog packages at the same time? Might be to migrate from one to the
>> other...
>
> I think usually not. But if so, we could make the table name configurable
> from the outside, e.g. in the Objects.yaml? Then you could resolve name
> clashes without modifying the actual vendor code.
>
> Greets Andi
>
>
> Andreas Förthner
> Leiter Web-Entwicklung
>
> Telefon: +49 (911) 539909 - 0
> E-Mail: andreas.foerthner at netlogix.de
> Website: media.netlogix.de
>
>
> --
> netlogix GmbH&  Co. KG
> IT-Services | IT-Training | Media
> Andernacher Straße 53 | 90411 Nürnberg
> Telefon: +49 (911) 539909 - 0 | Fax: +49 (911) 539909 - 99
> E-Mail: info at netlogix.de | Internet: http://www.netlogix.de
>
> netlogix GmbH&  Co. KG ist eingetragen am Amtsgericht Nürnberg (HRA 13338)
> Persönlich haftende Gesellschafterin: netlogix Verwaltungs GmbH (HRB 20634)
> Umsatzsteuer-Identifikationsnummer: DE 233472254
> Geschäftsführer: Stefan Buchta, Matthias Schmidt
>
>
>