'varchar(16) binary' works in 3.22 and tinyblob works in 3.23.
by work I mean I can insert hexidecimal numbers into the field.
I am basically treating it as an integer field. I can store 16 byte
numbers in the field and in the case of varchar(16) binary on mysql 3.22
I could store a 32 character
This works... however it does not fix my problem.
I did a little more research...
Instead of varchar(M) BINARY I can do a tinyblob.
This allows me to do the inserts and selects that I previously
mentioned.
Also the documentation says that you can consider blob as a varchar
binary.
So My qu
inserting 0x1 into a CHAR field?
- Original Message -
From: "Tommie Jones" <[EMAIL PROTECTED]>
To: "Rolf Hopkins" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Wednesday, February 07, 2001 22:18
Subject: Re: binary bug in mysql 3.23.30-gamma
> Bina
> Binary is an option on the varchar type
> I pulled the following quote from the mysql website.
>
> It just does not seem to be working anymore.
A guess:
It seems to me that the problem is not in
your colmn definition, but the silent type
conversions MySQL performs. In the log you
show below, y
Binary is an option on the varchar type
I pulled the following quote from the mysql website.
It just does not seem to be working anymore.
[NATIONAL] VARCHAR(M) [BINARY]
A variable-length string. NOTE: Trailing spaces are removed when the
value is stored (this differs from the ANSI SQL specificat
I think you are a bit confused with binary and varchar. varchar is used to
store strings such as "the cow jumped over the moon" and binary means that
it is case sensitive.
You are trying to insert a hex value of 0x1, right? I think this is an
illegal value and those two entries are set to NULL.
