Well, I've changed jobs, but the place where I was working was driving much of this development. I don't know what their future plans are, though, or if they might want to object, but I've copied the interested party from there. I'm sure they don't want to hold up development, but it seems a lot of catch up development will be required on other producers to get things back to where they were. Are there not some base class methods that could be used to provide the previous functionality?
Chris Jess Robinson wrote: > > Hi folks, > > Well, I did warn you.. I managed to find someone courageous enough to > poke big holes in the diffing code, and replace the bits that actually > output SQL, to use the producers instead. > > This means that some incompatible changes have been made, because Diff > used to do some things that are not in the respective producers. > > Please would people who need this code look at the new changes > (enclosed as patches, will apply them to cvs unless people yell loudly > enough ;), and update the relevant producers to be able to cope with > the needed changes? Should be fairly simple. The MySQL producer diff > is also attached as a working example. > > Thanks Luke!! > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ -- sqlfairy-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sqlfairy-developers
