A problem occurs with the InOperator when the collection exceds 2100 items

Hello Catalin,
Thank you for your report. Unfortunately, we cannot fix this problem in our code. The exception is thrown in the SqlClient classes. Please inform Microsoft about this problem.
The immediate solution to this issue is discussed in the following Knowledge Base article:
How to obtain a collection of persistent objects by a set of their IDs
Thank you,
Nick

Thank you Nick for your reply.
I tried to use the alternate solution you've indicated but unfortunately with no success for my case.
With all the respect I think this issue is a bug or at least a hidden limitation with the InOperator even if it is due to a SQLClient limitation.
I think you should consider fixing or at least publishing this limitation as it also cames from your underlying implementation that uses SQL parameters for the IN clause (the number of SQL parameters is limited to 2100).
In our network configuration management project we've made our persistent classes aware of an "NetworkContext" that gives the visibility of an object at some moment in time.
In order to implement the awarness in our classes I've overriden the XPBaseObject's "CreateCollection<T>" adding an additional criteria (the InOperator) to the contained collections :
…
        protected override XPCollection<T> CreateCollection<T>(XPMemberInfo property)
        {
            XPCollection<T> result = base.CreateCollection<T>(property);
            if (result.GetObjectClassInfo().ClassType.GetInterface(typeof(ISerializableWithFDNKeyRefs).Name) != null)
            {
                CriteriaOperator skimMergingCriteria;
                if (property.IsManyToMany)
                    skimMergingCriteria = getSkimMergingCriteria(property.Name);
                else
                    skimMergingCriteria = getSkimMergingCriteria("OID");

if (!ReferenceEquals(skimMergingCriteria, null))
                    skimHelperCriteria(result, skimMergingCriteria);
            }
            return result;
        }
        private static void skimHelperCriteria(XPBaseCollection collection, CriteriaOperator mergingCriteria)
        {
            XPCollectionHelper helper = getXPCollectionHelper(collection);
            Type helperType = helper.GetType();
            FieldInfo fi_fCriteria = helperType.GetField("fCriteria", BindingFlags.NonPublic | BindingFlags.Instance);
            CriteriaOperator fCriteria = (CriteriaOperator)fi_fCriteria.GetValue(helper);
            CriteriaOperator newHelperCriteria = CriteriaOperator.And(fCriteria, mergingCriteria);
            fi_fCriteria.SetValue(helper, newHelperCriteria);
        }
        private static XPCollectionHelper getXPCollectionHelper(XPBaseCollection collection)
        {
            Type collectionType = collection.GetType();
            FieldInfo fi_Helper = collectionType.GetField("Helper", BindingFlags.NonPublic | BindingFlags.Instance);
            if (fi_Helper == null)
                throw new Exception("helper not found. eXpressPersistentObject's version changed ? " + Environment.NewLine +
                                    "please contact the <skimHelperCriteria> author.");
            XPCollectionHelper helper = (XPCollectionHelper)fi_Helper.GetValue(collection);
            return helper;
        }
…
Briefly, I need a way to return an xpcollection OWNED by a persistent object applying also this criteria on the network context.
As I said, I tried to use the solution based on XPCursor but I found no way of specifying a criteria for the OWNER join.
Inspired by the XPO sources I've tried to use :
…
                    ownerJoinCriteria = new BinaryOperator(new OperandProperty(property.GetAssociatedMember().Name),
                                                           new OperandValue(this),
                                                           BinaryOperatorType.Equal);
…
but it won't work with ManyToMany associations (returns runtime error with the criteria and the property path)…
Please, can you help me with the OWNER criteria ?
Thank you.
Best regards,
Catalin Manoliu
Technical Project Leader
Audilog Groupe Ericsson for Bouygues Telecom
+33675718622
cmanoliu
@
bouyguestelecom.fr

Hello Catalin,
If I correctly understand your task, you can use this code to load a filtered collection of the Network objects owned by a given Owner (the "o" variable):

C#
using DevExpress.Xpo;  
using DevExpress.Data.Filtering;  

Owner o = XpoDefault.Session.FindObject<Owner>(null);  
CriteriaOperator filter = CriteriaOperator.Parse("OwnerLinks[This = ?] AND Domain = ?", o, "MyFirm");  
// the same filter in Simplified Criteria Syntax:  
filter = new OperandProperty("OwnerLinks")[new OperandProperty("This") == new OperandValue(o)] & new OperandProperty("Domain") == "MyFirm";  
XPCollection<Network> filteredNets = new XPCollection<Network>(filter);  

public class Owner : XPObject {  
    [Association("Owners-Networks")]  
    public XPCollection<Network> NetLinks {  
        get { return GetCollection<Network>("NetLinks"); }  
    }  
}  

public class Network : XPObject {  
    public string Domain;  

    [Association("Owners-Networks")]  
    public XPCollection<Owner> OwnerLinks {  
        get { return GetCollection<Owner>("OwnerLinks"); }  
    }  
}  

Thank you,
Nick

With this hint I think I shall be able to workaround the problem.
Thank you!
Best regards,
Catalin