The all-F's number in calculator is unsigned, and I bet BigInt is signed, so
you loose one bit. That generally means you have to divide by two and
subtract one to get the largest positive integer that fits.
Mark
-Original Message-
From: Tony Weeg [mailto:tony;navtrak.net]
Sent:
I think FF = 1 Byte = 8 Bits
AND = 8 Bytes = 64 Bits
18446744073709551615 = 2^64
However to account for negative numbers, 1 bit is used to determine if the
number is positive or negative. So, if I'm correct, the upper limit would be
2^64 or ~ 9.22337 * 10^18 (I can't calculate
: nrotbko: sql server big int
I think FF = 1 Byte = 8 Bits
AND = 8 Bytes = 64 Bits
18446744073709551615 = 2^64
However to account for negative numbers, 1 bit is used to determine if
the
number is positive or negative. So, if I'm correct, the upper limit
would be
2^64 or ~ 9.22337 * 10
Yep, it's a signed number...
Integer (whole number) data from -2^63 (-9223372036854775808) through 2^63-1
(9223372036854775807).
so that's your upper limit for the bigint field in mssql2000.
S. Isaac Dealey
Certified Advanced ColdFusion 5 Developer
www.turnkey.to
954-776-0046
The all-F's
, November 07, 2002 8:53 AM
To: CF-Talk
Subject: Re: nrotbko: sql server big int
I think FF = 1 Byte = 8 Bits
AND = 8 Bytes = 64 Bits
18446744073709551615 = 2^64
However to account for negative numbers, 1 bit is used to determine if the
number is positive or negative. So, if I'm
Personally I think bit-logic as a means of determining permissions for
application features is over-complicated, difficult to implement and/or
modify and seriously limits your options.
But then, that's not my decision to make. :)
My tendancy with roles and permissions is to use cross-reference
6 matches
Mail list logo
