×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Gentlemen, thanks for all of the replies. I probably won't get back to
this project until next week, but I wanted to acknowledge your
contributions. It's apparent I still have much to learn about this type of
stuff.
The biggest concern was, if I didn't use varchar, I'd always be passing
16MB of data to Qc3CalculateHash. 95% of the time, the length of the data
to be hashed won't exceed 100KB, but those outliers kill ya, so I
accommodate the max. Do I understand correctly that, by specifying
%addr(DataToHash:*DATA), that no data is being copied, but simply the
address of that data is passed to Qc3CalculateHash? If that's the case, I
wouldn't need to worry about defining DataToHash as varchar; just define it
as char. Do I have that right?
- Dan
As an Amazon Associate we earn from qualifying purchases.
This thread ...
Re: RNF7535: varchar not compatible with options(*varsize)?, (continued)
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
