×
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.
Charles Wilt wrote:
Just curious as to what guidelines you use when choosing between
signed or unsigned integer to replace the binary data type in API
calls.
IIRC, some of the APIs tell you rather the parameter is signed or
unsigned. But most don't.
When the API docs just say "BINARY", it means "signed".
The info center says this:
"In the API parameter tables, BINARY(2), BINARY(4), and BINARY(8)
represent numeric data. These parameters must be signed, 2-, 4-, or
8-byte numeric values with a precision of 15 (halfword), 31 (fullword),
or 43 bits and 1 high-order bit for the sign. Numeric parameters that
must be unsigned numeric values are explicitly defined as BINARY(x)
UNSIGNED."
As an Amazon Associate we earn from qualifying purchases.
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.