This all started when one of the 16 byte binary primary keys kicked out
a duplicate key error. It seems mysql does not store the last byte of
the binary value if it is a space. That is, ascii 32 or hex 20.
How do I force it to store the space? Thanks!
create table testtable ( id binary(16) NOT
In the last episode (Dec 03), Mark Maunder said:
This all started when one of the 16 byte binary primary keys kicked out
a duplicate key error. It seems mysql does not store the last byte of
the binary value if it is a space. That is, ascii 32 or hex 20.
How do I force it to store the
Thing is I don't want a dynamic table for performance reasons. I'm
storing an MD5 hash which is 16 bytes. As a workaround I'm only using 8
bytes of the hash and storing it in a bigint(20) column for now. So I
guess eighteen quintillion, four hundred forty six quadrillion, seven
hundred forty four
At 14:10 -0600 12/3/04, Dan Nelson wrote:
In the last episode (Dec 03), Mark Maunder said:
This all started when one of the 16 byte binary primary keys kicked out
a duplicate key error. It seems mysql does not store the last byte of
the binary value if it is a space. That is, ascii 32 or hex
So what you're saying is that BINARY isn't binary because it chomps
spaces off the end, thereby corrupting the binary data. Sounds like a
bug. Should I report it?
On Fri, 2004-12-03 at 12:30, Paul DuBois wrote:
I agree about using the TINYBLOB to avoid trailing space truncation, but
BINARY and
Mark,
- Original Message -
From: Mark Maunder [EMAIL PROTECTED]
Newsgroups: mailing.database.myodbc
Sent: Friday, December 03, 2004 10:52 PM
Subject: Re: if last binary byte is space (ascii 32) mysql drops it
So what you're saying is that BINARY isn't binary because it chomps
spaces off
