Wouldnt it be a hell of a lot easier to update jdbc and then get modules to follow suit. They are going to have to anyway sooner or later. Backporting the fix is only to make cite tests work against a single datastore I suspect? At some point we need to stop fixing old code, to create the drivers to move forward and free up resources to make the necessary move.
Justin Deoliveira wrote: > Hi all, > > I have spent some time rewriting the sql encoder for postgis to be based > off of the geoapi interface. While it yields a lot cleaner code, I had > some problems actually hooking it up to the datastore. > > Both postgis and jdbc are tightly coupled to it so using the new encoder > requires a lot of the same work required to break away postgis from > jdbc. Not trivial to say the least. > > So... I am stuck hacking at the old encoder :(. I have created a jira > task and attached the patches I would like to apply. > > http://jira.codehaus.org/browse/GEOT-1088 > > Review would be much appreciated. > > I will also be posting the implementation based off of the geoapi > FilterVisitor for review soon. > > Thanks, > > -Justin > > ------------------------------------------------------------------------- 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
