This is a quite common problem with the behaviors and one of the
reasons why they are not in the Doctrine 2 core.
In order to leverage the full power of the behaviors, my advice is try
to understand what is going on behind the scenes. In your case, you're
declaring the Versionable behavior before the I18n behavior. So, the
Versionable creates a plugin containing all the fields of your table,
then I18n removes your I18n fields from the table, and moves them to a
plugin of its own.
As for the Taggable behavior, my best guess is that it does not
support composite primary keys, and I do not see NestedSet anywhere in
your schema.
Anyway, if you understand the intricacies of the way behaviors are
implemented, they can be quite powerful, and I myself am using them
extensively like in the following scheme:
actAs:
I18n:
fields: [description]
actAs:
Versionable:
versionColumn: version
className: MyTranslationVersion
auditLog: true
deleteVersions: false
Sluggable:
unique: true
fields: [name]
Timestampable:
updated:
disabled: true
SoftDelete: ~
Deactivatable: ~
Versionable:
versionColumn: version
className: MyVersion
auditLog: true
deleteVersions: false
Duplicateable:
relations: [Attributes, Detail, Prices, Units, Seasons,
Translation]
Kind regards
Johannes
On Mar 19, 7:19 pm, Sid Ferreira <sid....@gmail.com> wrote:
> I forgot: thanks in advance :)
>
> On 19 mar, 15:13, Sid Ferreira <sid....@gmail.com> wrote:
>
> > Hi all!
> > Recently I've got a big disappointment with symfony 1.4.
>
> > With a new project, wich we expected to be able to use 100% of Symfony
> > and Doctrine combo, specially the behaviours of Doctrine.
> > Indeed, we made an exotic schema:
>
> > TableName:
> > actAs:
> > SoftDelete:
> > Timestampable:
> > Blameable:
> > Versionable:
> > I18n:
> > fields: [title, description]
> > actAs:
> > Timestampable:
> > Sluggable:
> > Blameable:
> > Versionable:
> > Taggable:
>
> > And ended up that we're facing this whole week tweaks to get over the
> > problems of using the combined behaviours:
> > - Versionable in the parenth table tried to add the translated fields
> > - Taggable can't save cause is missing lang (trying to find what's
> > wrong)
> > - Nested set methods doesn't show up
> > - Custom names for primary keys are many times ignored
>
> > Anyway, I got a lot of headache due to this issues, so Im wondering:
> > why the parts of the clock aren't working? Does anybody did this sort
> > of use of Doctrine and had similar problems?
>
> > Any help is acceptable
>
> > ps: I don't want to discuss Propel vs doctrine, it's just the first
> > project that I'm trying to use 100% of doctrine.
--
If you want to report a vulnerability issue on symfony, please send it to
security at symfony-project.com
You received this message because you are subscribed to the Google
Groups "symfony users" group.
To post to this group, send email to symfony-users@googlegroups.com
To unsubscribe from this group, send email to
symfony-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/symfony-users?hl=en
To unsubscribe from this group, send email to
symfony-users+unsubscribegooglegroups.com or reply to this email with the words
"REMOVE ME" as the subject.
