The documentation on paging says
Paging is disabled if you pass 0 for the page number or 0 or 1 for the page size.
My tests show it is not disabled, but instead treats a page number of 0 as if it were a page number of 1, honoring page size, rather than max number of records.
SD.LLBLGen.Pro.DQE.SqlServer: File Version 4.0.13.523
SD.LLBLGen.Pro.ORMSupportClasses: File Version 4.0.13.725
The following test passes all asserts, but the 3rd should fail,
[Test]
public void PagingTest01()
{
using (var adapter = new DataAccessAdapter())
{
int maxRecords = 200;
int pageNoZero = 0;
int pageNoOne = 1;
int pageSize = 100;
var invoiceId = 479937;
var rpb = new RelationPredicateBucket(LifelineDetailV2Fields.InvoiceId == invoiceId);
var sortExpression = new SortExpression(LifelineDetailV2Fields.RowId | SortOperator.Ascending);
var collection1 = new EntityCollection<LifelineDetailV2Entity>();
var collection2 = new EntityCollection<LifelineDetailV2Entity>();
var collection3 = new EntityCollection<LifelineDetailV2Entity>();
var collection4 = new EntityCollection<LifelineDetailV2Entity>();
adapter.FetchEntityCollection(collection1, rpb);
adapter.FetchEntityCollection(collection2, rpb,maxRecords,sortExpression);
adapter.FetchEntityCollection(collection3, rpb,maxRecords,sortExpression,pageNoZero,pageSize);
adapter.FetchEntityCollection(collection4, rpb, maxRecords, sortExpression, pageNoOne, pageSize);
Assert.AreEqual(517,collection1.Count);
Assert.AreEqual(200, collection2.Count);
Assert.AreEqual(100, collection3.Count);
Assert.AreEqual(100, collection4.Count);
var results = string.Format("collection1:{0}|collection2:{1}|collection3:{2}|collection4:{3}", collection1.Count, collection2.Count, collection3.Count,
collection4.Count);
Console.WriteLine(results);
Assert.AreEqual(collection3[0].RowId,collection4[0].RowId);
}
}