Gerald Luger writes:
> Shouldn't I expect all results to be 000...0001?
Well, no.
The SQL spec is pretty clear about the interpretation of this:
b'1'::bit(64)
You're taking a bit string of length 1 and casting it to bit string
of length 64. That's done by appending zeroes on the right,
On 5/31/2013 6:01 PM, Gavin Flower wrote:
SQL's BIT type is big endian, a hangover from its IBM mainframe
heritage.
I don't think it has anything to do with byte sex (I know of 3 ways to
store integers in memory, and I suspect there are more !).
I was thinking of bit sex, not byte.
IBM
On 01/06/13 13:01, Gavin Flower wrote:
On 01/06/13 12:29, John R Pierce wrote:
On 5/31/2013 4:29 PM, Gerald Luger wrote:
Shouldn't I expect all results to be 000...0001?
Otherwise it would be
1 != 1?
SQL's BIT type is big endian, a hangover from its IBM mainframe
heritage.
I don't thi
On 01/06/13 12:29, John R Pierce wrote:
On 5/31/2013 4:29 PM, Gerald Luger wrote:
Shouldn't I expect all results to be 000...0001?
Otherwise it would be
1 != 1?
SQL's BIT type is big endian, a hangover from its IBM mainframe heritage.
I don't think it has anything to do with byte sex (I
On 5/31/2013 4:29 PM, Gerald Luger wrote:
Shouldn't I expect all results to be 000...0001?
Otherwise it would be
1 != 1?
SQL's BIT type is big endian, a hangover from its IBM mainframe heritage.
--
john r pierce 37N 122W
somewhere on the middle of the
Shouldn't I expect all results to be 000...0001?
Otherwise it would be
1 != 1?
-Original Message-
From: Tom Lane [mailto:t...@sss.pgh.pa.us]
Sent: Friday, May 31, 2013 5:34 PM
To: Gerald Luger
Cc: pgsql-bugs@postgresql.org
Subject: Re: [BUGS] BUG #8191: Wrong bit conversion
ger...@hexboss.com writes:
> SELECT b'1'::bit(64), x'1'::bit(64), 1::bit(64)
> RESULT:
> "1000",
> "0001",
> "0001"
I
The following bug has been logged on the website:
Bug reference: 8191
Logged by: Gerald Luger
Email address: ger...@hexboss.com
PostgreSQL version: 9.2.1
Operating system: Windows 8
Description:
SELECT b'1'::bit(64), x'1'::bit(64), 1::bit(64)
RESULT:
"100