21 Jul
2010
21 Jul
'10
2:30 a.m.
On Tuesday 20 July 2010, Iñaki Baz Castillo wrote:
Hey Inaki,
yes, this is not the case at the moment.
This are indeed valid use cases, did not thought about it. Also the dialog
module outputs some bigger list, but normally not several 100k. ;-)
Regards,
Henning
another would
be to partition the command execution in small steps
like we do for data loading in several modules.
Yes, but this involves MI process to be designed for that, and it's
not the case, right? This is, in case the retrieved information
exceeds some size it should be automatically partitioned in various
steps which are sent to the MI process one by one. But as i said
earlier, its maybe not the best idea in general to pipe the
output of several houndred thousands rules through the MI interface,
especially if the information is available more or less similar in the
database.
Sure, but what about when using just memory (as in db_mode=0 for
usrloc)? Also there are other modules (as LCR) which just use the
database to load initial values and later those values or their
attributes are modified in memory (i.e: LCR gateways status).