Quick follow-up, Looks like property_view is a table not a view, turns out that "_view" means that it's a layer, attribute data is in a separate "table".
Also, on the performance of FeatureCollection vs. FeatureReader, it looks like the comparison wasn't necessarily fair, since the FeatureReader was returning only a particular column, the 'key' that we're trying to return, whereas the FeatureCollection test was returning everything, and it wasn't using the same code path as the initial problem I asked for help on, so that may be a red herring. Looks like I will need to have a closer look at the difference between the two to see if the FeatureCollection is returning the geometry like the FeatureReader option. Actually I guess it will be, since it's just returning everything, maybe it's doing lazy initialization of the geometry that isn't happening on the FeatureReader side. Cheers, Shaun
------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev
_______________________________________________ Geotools-gt2-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
