[Tree - Closure] Issue enabling APC cache

[comfortablynumb]

Hi,

Using extensions from master branch (updated a week ago or so) and enabling APC Cache I get the following exception, which is not thrown if I disable it:

[Semantical Error] line 0, col 103 near 'descendant WHERE': Error: Class Entity\EntityClosure has no association named descendant

Am I doing something wrong here? or maybe I'm missing something?

Thanks in advance.

[l3pp4rd]

I think it is really an issue, since I forgot that onMetadataLoad event is never triggered if cache is used. Users will have to map their closures manually. Today I have a bunch of new issues reported, it was so quite for a month or two :) now I don't think that I will be able to fix it before the weekend. For now you can map it manually using annotations or whatever.

[comfortablynumb]

Hey, don't worry! there's no rush :) It's awesome to have these extensions already working. And they work really great! I'd like to help with this type of issues but I'm not familiarized a lot with Doctrine 2 internals yet, and my actual project is really eating my time. But as soon as I finish this app I'll try to help wherever I can, being the performance issue of the closure strategy you mentioned sometime ago the first topic I'll try to help with.

Again, thanks a lot!

[stof]

As the user still need to define the Closure entity, I guess it could be an acceptable solution to require it to map the associations manually for now as long as it is well documented.

[l3pp4rd]

Yes, we will need to add some examples in docs. So far nested set also needs specifying cascade on delete for parent, and I see that users pretty much just copies the example and it works well. Also it will allow advanced users to add additional cascades if they need them, or specify whether to fetch lazily or eagerly. So in my opinion this is indeed less magic and more customizability

[comfortablynumb]

I agree with you guys. I think making the mapping configuration explicit for the closure entity is the way to go. It's much more clear that way, it avoids confusion and it lets the user, as said before, customize the closure entity.

So, +1 for me.

[l3pp4rd]

the problem with manual mapping is that, listener must know which fields are ancestor and descendant in closure entity. I surely do not want to add additional annotations just for that, any ideas?

[l3pp4rd]

@comfortablynumb check if it works on master branch. I have not added a manual mapping since it introduces more complications :)

[comfortablynumb]

Sorry for the delay. I'll give it a try as soon as I can update my app's vendors (including these extensions) and my app accordingly. I'm stuck with some other stuff right now, but I'm planning to do it in the next few days.

Thanks a lot for your help!

[l3pp4rd]

np, try it when you have time

[comfortablynumb]

Hi,

Just wanted to say that today I've finally updated my app's vendors, including your extensions. Sorry for the delay to answer. It took me some days to finally have time to update everything. The issue is gone :) thanks a lot!