DistinctFilteringPreferenceType Enumeration |
Namespace: SD.LLBLGen.Pro.ORMSupportClasses
Member name | Value | Description | |
---|---|---|---|
System | 0 | Emit Distinct into the SQL query using the rules embedded in the code (default). | |
AlwaysClientSide | 1 | Always use client-side Distinct filtering. This can be CPU intensive with large sets of duplicates, however on databases where DISTINCT is very time consuming, this setting can be an optimization. | |
Legacy | 2 | Use the v2.6 rules set for emitting distinct. Similar to 'System', but with one exception: if the relationships specified contain m:1 or 1:1 relationships, it will see the resultset as 'unique rows' and will use that into account when emitting Distinct and TOP for entity fetches. This option can give wrong results (no distinct emitted while it should emit distinct). In that case, use 'System' (recommended). |
(c)2002-2018 Solutions Design bv