[CAY-767] "fetchLimit" unaccounted when calculating cache key

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 3.0
• Fix Version/s: 3.0
• Component/s: Core Library
• Assignee: Andrus Adamchik
• Reporter: Andrus Adamchik
• Created: 12/Mar/07 14:28
• Updated: 12/Mar/07 15:29
• Resolved: 12/Mar/07 15:29

Description

This is a minor bug that affects 3.0 only.

SelectQuery automatically builds a cache key for the caching result based on its parameters.

It fails to take into account fetchLimit, thus leading to erratic behavior when different fetch limits are used for the same query.