[symfony-users] Re: Propel nested set and sfOutputEscaperIteratorDecorator - too many queries
On 27 Apr, 18:27, Rytis Daugirdas rytis.daugir...@gmail.com wrote: Since when iterators are overkill? IMO, your suggestion is overkill. Propel documentation clearly states that a tree can be easily traversed via its iterator interface. Why should I write additional code (however simple) to get the functionality that is already provided? Besides, since I need the level of each node, your suggestion is not suitable as it too makes query count depend on the number of nodes retreived. Well, it's just my opinion. You don't need to write additional code, the retrieveTree() method already retrieve the entire tree, with all levels calculated, in one query. cheers Massimiliano -- 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
[symfony-users] Re: Propel nested set and sfOutputEscaperIteratorDecorator - too many queries
On 26 Apr, 18:11, Rytis Daugirdas rytis.daugir...@gmail.com wrote: To output a list of nodes, obviously. It looks a bit overkilled to me. Just retrieve the whole table ordered by left, and you'll get the entire tree. cheers Massimiiano -- 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
[symfony-users] Re: Propel nested set and sfOutputEscaperIteratorDecorator - too many queries
Massimiliano, Since when iterators are overkill? IMO, your suggestion is overkill. Propel documentation clearly states that a tree can be easily traversed via its iterator interface. Why should I write additional code (however simple) to get the functionality that is already provided? Besides, since I need the level of each node, your suggestion is not suitable as it too makes query count depend on the number of nodes retreived. On Apr 27, 4:48 pm, Massimiliano Arione garak...@gmail.com wrote: On 26 Apr, 18:11, Rytis Daugirdas rytis.daugir...@gmail.com wrote: To output a list of nodes, obviously. It looks a bit overkilled to me. Just retrieve the whole table ordered by left, and you'll get the entire tree. cheers Massimiiano -- 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 athttp://groups.google.com/group/symfony-users?hl=en -- 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
[symfony-users] Re: Propel nested set and sfOutputEscaperIteratorDecorator - too many queries
It's not clear to me why you want to use an iterator in a template. cheers Massimiliano On 26 Apr, 10:56, Rytis Daugirdas rytis.daugir...@gmail.com wrote: Hello, When using Propel's nested set behaviour, iteration over a node set in a template (with output escaping enabled) produces too many queries. Here's an example:http://pastebin.com/KTzDfvwd Using the unescaped iterator works fine. Is that a bug in sfOutputEscaperIteratorDecorator? If not, how should the problem be solved? Regards, Rytis -- 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 athttp://groups.google.com/group/symfony-users?hl=en -- 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
[symfony-users] Re: Propel nested set and sfOutputEscaperIteratorDecorator - too many queries
To output a list of nodes, obviously. On Apr 26, 4:20 pm, Massimiliano Arione garak...@gmail.com wrote: It's not clear to me why you want to use an iterator in a template. cheers Massimiliano On 26 Apr, 10:56, Rytis Daugirdas rytis.daugir...@gmail.com wrote: Hello, When using Propel's nested set behaviour, iteration over a node set in a template (with output escaping enabled) produces too many queries. Here's an example:http://pastebin.com/KTzDfvwd Using the unescaped iterator works fine. Is that a bug in sfOutputEscaperIteratorDecorator? If not, how should the problem be solved? Regards, Rytis -- 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 athttp://groups.google.com/group/symfony-users?hl=en -- 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 athttp://groups.google.com/group/symfony-users?hl=en -- 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
