From: Jeff Smelser
Date: October 20 2005 1:15pm
Subject: Re: ARCHIVE storage engine and INSERT DELAY in MySQL 4.1
List-Archive: http://lists.mysql.com/mysql/190637
Message-Id: <200510200815.49218.tradergt@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed;
  boundary="nextPart16615549.d0eZdSpQua";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart16615549.d0eZdSpQua
Content-Type: text/plain;
  charset="windows-1251"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Wednesday 19 October 2005 04:34 pm, Mihail Manolov wrote:

> It's the way our code is written, and I just changed the table type and
> began getting this error. We have lots of data to insert into this
> table, therefore the optimal option is to use DELAYED and insert them in
> blocks.
>
> Not sure why they say that ARCHIVE storage engine is a new feature in 5.0?

I had to take a double take, as I thought it was.. That could be why its no=
t=20
working 100%, as its actually a feature of 5.0. However, I am guessing that=
=20
this point..

Jeff

--nextPart16615549.d0eZdSpQua
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQBDV5iFoOk9EvUvEtgRAr54AJ9ay/kW7JZxZCDwZHXQF5ZOBqgD8gCg4uRx
WKkPR/Uvwnjk2zBEXi2fB8A=
=TGA8
-----END PGP SIGNATURE-----

--nextPart16615549.d0eZdSpQua--