Jody Garnett ha scritto: > Perfect! This is exactly the kind of thing I was hoping for as we set up > FeatureList. > > FeatureCollection.sort( SortBy ).iterator() should give you a "sorted > writer". The iterator should let you work over top of a sorted result > set :-)
I have a preference for working against FeatureReader and FeatureWriter because they're simpler and more predictable imho, so I would really like a public DataStore call that sounds like: FeatureWriter getFeatureWriter(String typeName, Filter filter, SortBy[], Transaction transaction) In the end, I believe we need the same thing, since to implement FeatureList you need the datastore to provide you some way to sort writers, no? Oh, btw, you said FeatureCollection.sort( SortBy ).iterator() gives me a sorted writer? You do mean that every time I do call next() a call to write() against the wrapped writer is implied? Moreover, the (nicer imho) FeatureIterator does not have a remove() call, we should add it then? Cheers Andrea ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
