headers
Francois Zaninotto | 16 Mar 2009 11:39
Picon
Gravatar

Nested set bug / Trac account request

Hi list,

I can't create a ticket on the Propel Trac, it seems rejected because of SPAM.

Could I have a Trac account please?

Cheers,

Francois

P.S.: As a side note, here is the bug report I want to file:

[Nested sets] Object instance pooling and moveToXXX() can't stand each other
---------------------------------------------------------------------------------------------------------

The `moveToXXX()` methods update the table records for left and right
value (in `NestedSetPeer::updateDBNode()` and the loaded objects for
left and right properties (in `NestedSetPeer::updateLoadedNode()`).

But some methods of NodeObjects use an internal cache which is NOT
refreshed by `NestedSetPeer::updateLoadedNode()`. That introduces
problems when inspecting a moved node.

Example use case:

{{{
$root = new Folder();
FolderPeer::createRoot($root);
$root->save();
(Continue reading)

Permalink | Reply |
headers
Heltem | 16 Mar 2009 20:49
Picon

Re: Nested set bug / Trac account request

Hans,

Can you provide him an account ?

Heltem

Francois Zaninotto a écrit :
> Hi list,
>
> I can't create a ticket on the Propel Trac, it seems rejected because of SPAM.
>
> Could I have a Trac account please?
>
> Cheers,
>
> Francois
>
> P.S.: As a side note, here is the bug report I want to file:
>
> [Nested sets] Object instance pooling and moveToXXX() can't stand each other
> ---------------------------------------------------------------------------------------------------------
>
> The `moveToXXX()` methods update the table records for left and right
> value (in `NestedSetPeer::updateDBNode()` and the loaded objects for
> left and right properties (in `NestedSetPeer::updateLoadedNode()`).
>
> But some methods of NodeObjects use an internal cache which is NOT
> refreshed by `NestedSetPeer::updateLoadedNode()`. That introduces
> problems when inspecting a moved node.
>
(Continue reading)

Permalink | Reply |

Gmane