Linear Hash Bug (Network Product)
At 23 NOV 2009 10:29:46AM chip fichot wrote:
Mike -
In light of the following serious bug in the software that seriously effects the integrity of our systems:
"In UD 4.6 we have enhanced the support for large key sizes and large records." said Michael Ruane, President and CEO of Revelation Software. "There are certain situations where parts of the system would handle it correctly and other parts may have treated it as a bug, giving you false errors." The Universal Driver 4.6 will no longer support unlimited-length record keys. Record keys can now be a maximum of 512 characters long. Any keys that exceed this limit will now be illegal and applications will be unable to either read or write them. A critical issue that has been addressed is the "Fix GFEs" option on the Verify LH menu silently considers any records with keys greater than 50 characters long to be GFEs. Anyone running the "Fix GFEs" option will lose any records that have keys longer than 50 characters. As a result of this issue, Revelation is including with the Universal Driver 4.6 a RDK containing a FIX_LH routine. This updated routine removes the "50-character-throwaway" functionality and replaces it with the "512-character-save" functionality."
Would the only way to address this bug be to purchase the 4.6 upgrade, or do you have other plans to patch or otherwise address this issue for earlier UD versions?
Thanks
Chip
At 23 NOV 2009 01:15PM Jared Bratu wrote:
What OpenInsight and network product version is in use at your site?
This is only an issue if you have records longer than 50 characters and use the Fix_LH routine. A scan of your attached tables to check for key length would reveal any potential problems. If your keys are under 50 characters there is no issue.