Hi
I will confirm with Zyne which syntax is correct and ensure that this
is merged to trunk, and i'll keep chtito posted so he can implement
this in schema.yml when its finalised. I think it will be using the
options method, so if a universal approach to this is added to
schema.yml this will probably be the best approach.
Thanks
Joe
On 2 Feb 2007, at 19:40, chtito wrote:
>
> This question has indeed been asked several times, there is also a
> ticket about it. As far as i can tell, the actsAsTree method is empty,
> in the Doctrine_Record class, which means that hierarchical data is
> not yet fully supported in Doctrine (despite the documentation
> claiming otherwise). The right person to ask is Joe Simms since he
> implemented some, or all the hierarchical data code in Doctrine.
>
> I will implement this in schema.yml as soon as everybody has agreed
> upon which syntax is best (Joe thought about "actsAsTree", but zyne
> preferred "option"... there is a second ticket about that for
> sfDoctrine :-P). When everything is ready, i'll implement model
> building accordingly.
>
> On 2 fév, 17:40, "Pierre Minnieur" <[EMAIL PROTECTED]
> project.com> wrote:
>> Hi,
>>
>> as I can see the Doctrine Team added support for hierarchical data in
>> form of a NestedTree implementation (two more will follow I guess
>> from
>> the sources).
>>
>> Now I'm asking, is automatic support for Trees in the schema.yml
>> (like: _attributes: { isTree: true, treeImpl: NestedSet, treeOpts:
>> { foo: bar } } on your ToDo list or have anybody ever asked about
>> that? If not, I do so! ;-)
>>
>> Cheers,
>> Pierre
>
>
> >
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"symfony developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/symfony-devs?hl=en
-~----------~----~----~----~------~----~------~--~---
