original bugid: #2910
So not on all nodes of a list, because most of them will probably not get used anyway.
The current situation will rather kill all performance if you would e.g. issue a list on 'object' in tje jsp-editors.
Perhaps this behavior should be moved from MMObjectBuilder to MMObjectNode or something like that.
CORRECT_NODE_TYPES should only be done on nodes which are actually used.
So not on all nodes of a list, because most of them will probably not get used anyway.
The current situation will rather kill all performance if you would e.g. issue a list on 'object' in tje jsp-editors.
Perhaps this behavior should be moved from MMObjectBuilder to MMObjectNode or something like that.
Michiel Meeuwissen added a comment - 2002-09-28 00:14 CORRECT_NODE_TYPES should only be done on nodes which are actually used.
So not on all nodes of a list, because most of them will probably not get used anyway.
The current situation will rather kill all performance if you would e.g. issue a list on 'object' in tje jsp-editors.
Perhaps this behavior should be moved from MMObjectBuilder to MMObjectNode or something like that.
CORRECT_NODE_TYPES should only be done on nodes which are actually used.
So not on all nodes of a list, because most of them will probably not get used anyway.
The current situation will rather kill all performance if you would e.g. issue a list on 'object' in tje jsp-editors.
Perhaps this behavior should be moved from MMObjectBuilder to MMObjectNode or something like that.
Eduard Witteveen added a comment - 2002-10-08 20:03 CORRECT_NODE_TYPES should only be done on nodes which are actually used.
So not on all nodes of a list, because most of them will probably not get used anyway.
The current situation will rather kill all performance if you would e.g. issue a list on 'object' in tje jsp-editors.
Perhaps this behavior should be moved from MMObjectBuilder to MMObjectNode or something like that.
Hi Michiel, do you know by hard whether this issue is still open? If so, please move it to 1.9 (imo it should not be part of a bugfix release) Thanks, Henk.
Henk Hangyi added a comment - 2007-02-25 14:03 Hi Michiel, do you know by hard whether this issue is still open? If so, please move it to 1.9 (imo it should not be part of a bugfix release) Thanks, Henk.
I suppose principally this bug is still open. Practicly tough, the consequences can be largely avoided since MMBase 1.7, because you can more easily limit the actual resultset size, as is done e.g. in generic editors.
Michiel Meeuwissen added a comment - 2007-02-25 17:02 I suppose principally this bug is still open. Practicly tough, the consequences can be largely avoided since MMBase 1.7, because you can more easily limit the actual resultset size, as is done e.g. in generic editors.
So not on all nodes of a list, because most of them will probably not get used anyway.
The current situation will rather kill all performance if you would e.g. issue a list on 'object' in tje jsp-editors.
Perhaps this behavior should be moved from MMObjectBuilder to MMObjectNode or something like that.