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

[Regine Rosewich]

Hi Dawid,

if you internalise the object oriented paradigm, you won't have any problem
because you would reuse the first post object for the second usage and only
extend it if necessary. The extension would cause the Doctrine2 Persistence
to extend the 'post' table according to the extended object. If you really
worked with two post objects within the same Application-Domain Doctrine2
should throw an error (I did not yet test such a constellation). The only
way to handle such a situation would be to work with two Settings.yaml, each
in the Configuration folder of the particular application. But then it would
be a little complicated to merge the data of the two databases if necessary.

To cut the chase: I would either try to reuse the first post-class (My
preference) or name the second post-class or both post-classes differently
(e. g. <Application1>_post and <Application2>_post).

Regine


-----Ursprüngliche Nachricht-----
Von: flow3-general-bounces at lists.typo3.org
[mailto:flow3-general-bounces at lists.typo3.org] Im Auftrag von Dawid
Pacholczyk
Gesendet: Montag, 21. März 2011 14:44
An: flow3-general at lists.typo3.org
Betreff: [FLOW3-general] Diffrent packages with simillar models + Doctrine

Hello List,
  for example I want to create a sociall application that is supporting 
Blog and Forum. Both Packages will contain DIFFRENT Post models. 
Doctrine is creating a table with the same name as model. How will it 
act if I`ll have to packages with Post model ?

Best regards,
Dawid Pacholczyk
_______________________________________________
FLOW3-general mailing list
FLOW3-general at lists.typo3.org
http://lists.typo3.org/cgi-bin/mailman/listinfo/flow3-general