Hi,
I just experienced the following bug in tables created as berkeley
tables:
on bdb tables:
mysql> SELECT
jobs.number,jobs.status,jobs.filename,jobs.source_file,verarbeitung.name
FROM verarbeitung right join jobs on (verarbeitung.verarbeitung =
jobs.verarbeitung) order by jobs.number;
+--------+--------+---------------------------+----------------------------------------------+------+
| number | status | filename |
source_file | name |
+--------+--------+---------------------------+----------------------------------------------+------+
| 1 | 1 | NULL |
NULL | NULL |
| 2 | 1 | /u/lpqueues/debis/data.40 |
/etc/hosts | NULL |
| 3 | 1 | /u/lpqueues/debis/data.41 |
/etc/hosts | NULL |
| 4 | 1 | /pfad/zum/datenfile |
DEFSYSM.SAF0006.SAF00066.JOB07513.D0000103.? | NULL |
| 5 | 1 | /pfad/zum/ogottogott |
DEFSYSM.SAF0006.SAF00064.JOB07514.D0000103.? | NULL |
+--------+--------+---------------------------+----------------------------------------------+------+
5 rows in set (0.15 sec)
on isam,bdb tables:
mysql> SELECT
jobs.number,jobs.status,jobs.filename,jobs.source_file,verarbeitung.name
FROM verarbeitung right join jobs on (verarbeitung.verarbeitung =
jobs.verarbeitung) order by jobs.number;
+--------+--------+----------------------+----------------------------------------------+--------+
| number | status | filename |
source_file | name |
+--------+--------+----------------------+----------------------------------------------+--------+
| 1 | 1 | NULL |
NULL | NULL |
| 2 | 1 | /pfad/zum/datenfile |
DEFSYSM.SAF0006.SAF00066.JOB07513.D0000103.? | ICOM |
| 2 | 1 | /pfad/zum/datenfile |
DEFSYSM.SAF0006.SAF00066.JOB07513.D0000103.? | CR->LF |
| 3 | 1 | /pfad/zum/ogottogott |
DEFSYSM.SAF0006.SAF00064.JOB07514.D0000103.? | CR->LF |
| 4 | 1 | /pfad/zum/datenfile |
/etc/hosts | NULL |
+--------+--------+----------------------+----------------------------------------------+--------+
5 rows in set (0.15 sec)
This is on mysql 3.23.47, I did not use exactly be same rows in the
comparison above but get the point. Just compare the rows with filename
= "/pfad/zum/ogottogott" in both select statements. The information in
the jobs and verarbeitung table are identical and the tables have been
created this way for the second select statement, for the first
statement they both have been created using bdb:
drop table if exists verarbeitung;
create table verarbeitung (
id int auto_increment not null primary key,
verarbeitung int,
priority int,
name char(50),
submission timestamp,
filename char(100),
params char(255)) type=isam;
drop table if exists jobs;
create table jobs (
number int auto_increment not null primary key,
queuename char(50),
verarbeitung smallint default 0,
status smallint default 0,
submission timestamp,
filename char(100),
host_name char(32),
user_name char(32),
job_name char(100),
class_banner char(32),
print_banner char(32),
free_file char(32),
source_file char(132),
printf_format char(32),
printf_unformat char(32),
optionT char(132),
datat char(2),
fileformat char(7),
cc char(4),
cctype char(2),
chars char(18),
pagedef char(9),
trc char(4),
ff char(9),
cop smallint default 1,
jobn char(9),
us char(9),
no char(9),
pr char(32),
ro char(32),
forms char(5),
class char(2),
destination char(9)) type=bdb;
Is it in general dangerous to use bdb tables?
Best regards,
Carsten Hammer
---------------------------------------------------------------------
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
