Haryana wrote:
> I have a job to make a mail server that store mail
> data in mysql table.
I was under the impression that the MySQL API does not have a
proper BLOB interface. Access to data in a BLOB is limited by the
max_packet parameter and therefore a BLOB larger than that cannot
be retrieve
databases enforced referential
integrity only on commit to allow precisely for such scenarios
as you describe, but I may be wrong.
Kristian
--
Kristian Köhntopp, NetUSE AG, Dr.-Hell-Straße, D-24107 Kiel
Tel: +49 431 386 435 00, Fax:
[EMAIL PROTECTED] wrote:
> This seems to be a competability feater, so you can load it into db2,
> oracle etc.
But not into MySQL - great idea. :-)
Kristian
--
Kristian Köhntopp, NetUSE AG Siemenswall, D-24107 Kiel
Tel: +49 431 386 436 00, Fax: +49 431 386
Kristian Köhntopp wrote:
> Short version: mysqldump seems to produce a "KEY mid(mid)"
> statement, which mysql does not understand. Using
> KEY (mid) instead of KEY mid(mid) works, though.
>
> Is this a known problem? Is this an oversight by me?
Ultrashort resolution:
default '',
-> mimetype varchar(255) NOT NULL default '',
-> changed timestamp(14) NOT NULL,
-> PRIMARY KEY (did),
-> KEY (mid)
-> ) TYPE=MyISAM;
Query OK, 0 rows affected (0.01 sec)
Kristian
--
Kristian Köhntopp, NetUSE AG Siemenswall, D-2
