For most things like this a on the order of hundreds it's not a big
deal. For thousands you might run into a problem, but it depends on
the database. For much above that I'd say using a join in the
database and letting it handle it would be far more efficient, even
though less flexible and such.
-David
On Aug 29, 2006, at 6:55 PM, Si Chen wrote:
Is there any theoretical limit on entityoperator.in -- ie, how
large a list it can take? I'm thinking of re-factoring the
ViewFacilityInventory report in facility to use this instead of
joining on productcategorymember so that it can be used to pull
variants of virtual products as well, but sometimes there could be
a lot of variants and a pretty large list -- a few hundred
products, etc.
Si
