From: Chris H. <ch...@op...> - 2007-03-08 22:56:23
|
Well thank you! (I wrote it, and was told that it was no longer good enough) The justification I got was that the superlongnamedvisitor had more potential for extensibility, that in theory it'd be able to handle filters better. Which I concede, as sqlencoder isn't designed for filters, but as of yet there's not much filter stuff in the visitor thing. I was fine to have it deprecated since it doesn't make sense to have two things that do basically the exact same thing. I never got a clear explanation as to why it was written in the first place, I know it was for the WFSDatastore. But it's used in PostGIS now, which is when I got the above explanation. Chris Farber, Saul (ENV) wrote: > This is kind of a targeted question, but I'll throw it out to the list to see if anyone else can answer too. > > Why is SQLUnpacker deprecated? > > Looking at PostPreProcessFilterSplittingVisitor the only thing I can figure that it's doing that SQLUnpacker isn't doing is handling client-side transactions via a ClientTransactionAccessor. > > Is there something fundamentally flawed about SQLUnpacker? I do have to say that SQLUnpacker is MUCH more clearly and concisely written. > > --saul > > ------------------------------------------------------------------------- > 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 > Geo...@li... > https://lists.sourceforge.net/lists/listinfo/geotools-devel > > !DSPAM:1003,45f090bb178271995013331! > -- Chris Holmes The Open Planning Project http://topp.openplans.org |