Hello,
There must have been some changes in the default interpretation
respective to foreign key attributes
If I add explicitly 'not null' to the columns host_id and admin_id
in test_nkomp_admin, it works like intended:
create table test_nkomp_admin
(
host_id int unsigned not null,
admin
Some more testing performed and it seems like problem with foreign key
reference indexing, see below:
create table test_nkomp_admin2
(
host_id int unsigned,
admin_id varchar(15),
foreign key (host_id) references test_nkomp (host_id) on delete
cascade on update cascade
)engine=innodb;
crea
On 10/28/2010 03:34 PM, misiaQ wrote:
Works fine on 5.0.87 (rows returned as expected).
Confirmed on 5.1.51-log.
Most likely problem with VARCHAR behavior, because this one works fine:
select * from test_nkomp_admin where host_id=6 and trim(admin_id)='luke';
The thing with the varchar was also
Works fine on 5.0.87 (rows returned as expected).
Confirmed on 5.1.51-log.
Most likely problem with VARCHAR behavior, because this one works fine:
select * from test_nkomp_admin where host_id=6 and trim(admin_id)='luke';
Regards,
m
-Original Message-
From: gregor kling [mailto:gregor.kl
