'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 hexidecimal number in a 16 byte field and
use it as a unique identifier.
We have several databases on different servers that are eventually
merged and to keep records unique we would use a combination ip address,
timestamp (and a few other features) to keep the primary keys unique.
This is old code that is too large to change in production.
Rolf Hopkins wrote:
>
> Working anymore? You mean that it used to work? Now I'm confused!!
>
> The quote from the manual is correct. Using BINARY means that 'A' < 'a' not
> 'A' = 'a' which is the case without the keyword BINARY.
>
> What is it you are trying to achieve by inserting 0x1 into a CHAR field?
>
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
