Non SQL encodable filter portions interact badly with offset/limit support --------------------------------------------------------------------------
Key: GEOT-2865 URL: http://jira.codehaus.org/browse/GEOT-2865 Project: GeoTools Issue Type: Bug Components: data jdbc-ng Affects Versions: 2.6.0 Reporter: Andrea Aime Assignee: Andrea Aime Fix For: 2.6.1 When a filter is split and the non encodable part is not Fitler.INCLUDE native support for offset/limit should be disabled and performed in memory instead. The reason is, the encodable filter part retrieves more features than the original one, in general, the native limit makes sure only N are returned, but the in memory filter will then return less than N to the caller. Long story short, the limit/offset should be removed and replaced with an in memory support (given data is supposed to be sorted, that is not hard to implement). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel