If I am not mistaken I think you are trying to do a nested select.
This is not possible in Mysql. I've had similar problems.
You will have to use some sort of recursive algorithm in your perl code
(if you are using perl)
to accomplish this.
Phil Latio wrote:
>
> I hope somebody may of come acro
'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
gt; 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. MySQL behaves
> > > differently from standard in that it inserts default values instead, if
> > > there is an error, which in your cas
is is an
> illegal value and those two entries are set to NULL. MySQL behaves
> differently from standard in that it inserts default values instead, if
> there is an error, which in your case, would be NULL. What you want instead
> is an integer column.
>
> - Original Message
In the process of converting over to 3.23.30-gamma from 3.22
whenever I set the field to a binary field to a value it stores it in
the database as zero.
Does anyone have any suggestions.
I am having a problem with the binary data type... Here is the log to
demonstrate.
---
In the process of converting over to 3.23.30-gamma from 3.22
It appears that a table with field 'key varchar(16) binary' as a
primary key.
Whenever I write a record to this table and then do a select the value
of the field seems to be zero.
I do a 'select * from table where key=0x0' I get all t
