At 8:50 -0800 11/7/03, Herb Rubin wrote:
Paul,
TINYBLOB does seem to hold the value properly.
I can't use a TINYBLOB in a primary key. Is this not allowed?
The ALTER statement complains that I am using a column without a length
specified.
Specify a length, then. :-)
http://www.mysql.com/doc/en/I
At 10:49 -0800 11/7/03, William R. Mussatto wrote:
Paul DuBois said:
At 15:29 -0800 11/6/03, Herb Rubin wrote:
Paul,
I did try VARCHAR(16) BINARY and it still failed to INSERT in a NOT
NULL column.
The encrypted string seems to be equivalent to the NULL value even
though it visually looks like
Hi William,
- Original Message -
From: "William R. Mussatto"
Sent: Friday, November 07, 2003 12:49 PM
Subject: Re: aes encryption bug
> Paul DuBois said:
> >
> > Okay, I investigated this further and I believe I know the cause of
the
> > problem. The so
t: Re: aes encryption bug
Paul,
TINYBLOB does seem to hold the value properly.
I can't use a TINYBLOB in a primary key. Is this not allowed?
The ALTER statement complains that I am using a column without a length
specified.
Herb
On Thu, 2003-11-06 at 19:24, Paul DuBois wrote:
> At 15:29 -
Paul,
Is there a limitation on having a TINYBLOB as a primary key?
Herb
On Thu, 2003-11-06 at 19:24, Paul DuBois wrote:
> At 15:29 -0800 11/6/03, Herb Rubin wrote:
> >Paul,
> >
> >I did try VARCHAR(16) BINARY and it still failed to INSERT in a NOT NULL
> >column.
> >
> >The encrypted string see
Paul DuBois said:
> At 15:29 -0800 11/6/03, Herb Rubin wrote:
>>Paul,
>>
>>I did try VARCHAR(16) BINARY and it still failed to INSERT in a NOT
>> NULL column.
>>
>>The encrypted string seems to be equivalent to the NULL value even
>> though it visually looks like some kind of data.
>>
>>Herb
>
> Ok
Paul,
TINYBLOB does seem to hold the value properly.
I can't use a TINYBLOB in a primary key. Is this not allowed?
The ALTER statement complains that I am using a column without a length
specified.
Herb
On Thu, 2003-11-06 at 19:24, Paul DuBois wrote:
> At 15:29 -0800 11/6/03, Herb Rubin wrote:
At 15:29 -0800 11/6/03, Herb Rubin wrote:
Paul,
I did try VARCHAR(16) BINARY and it still failed to INSERT in a NOT NULL
column.
The encrypted string seems to be equivalent to the NULL value even though
it visually looks like some kind of data.
Herb
Okay, I investigated this further and I believe
Paul,
I did try VARCHAR(16) BINARY and it still failed to INSERT in a NOT NULL
column.
The encrypted string seems to be equivalent to the NULL value even though
it visually looks like some kind of data.
Herb
> Please reply to the list, not to me directly, so that others can
> follow this dis
Please reply to the list, not to me directly, so that others can
follow this discussion. Thanks.
At 14:54 -0800 11/6/03, Herb Rubin wrote:
Paul,
Yes, I get the same, now try and decrypt it, it will turn out to be NULL.
So, you cannot insert this into a NOT NULL column. It will reject it.
Your mes
At 14:03 -0800 11/6/03, Herb Rubin wrote:
Hi,
I am trying to use aes_encrypt and I get a NULL value with a specific
string:
INSERT INTO test SET
`id` = AES_ENCRYPT('551850040', '0bf251c9aaf007deaf1143ca1492b561');
my field 'id' is VARCHAR(16) NOT NULL
If I change the value or the encryption strin
Hi,
I am trying to use aes_encrypt and I get a NULL value with a specific
string:
INSERT INTO test SET
`id` = AES_ENCRYPT('551850040', '0bf251c9aaf007deaf1143ca1492b561');
my field 'id' is VARCHAR(16) NOT NULL
If I change the value or the encryption string it works. But this
combination turn
12 matches
Mail list logo