-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
>> ------------------------------------------------------------
>> mi_int4store(ptr,base->pack_reclength); ptr +=4;
>> Is this the average for a packed record? If so, how is it computed? If I
>> do not pack the data file, then pack_reclength is equal to reclength,
>> isn't it?
>
> How it's computed - see mi_create.c.
> It's equal if there's no live checksum, and pack_reclength
> is not less than rec_reflength.
>
> Not the average, it's basically the reclength above without
> rec_reflength/checksum correction.
Hm, I looked at the source code and found:
share.base.reclength=real_reclength;
share.base.pack_reclength=reclength+ test(options & HA_OPTION_CHECKSUM);
For me this looks like that pack_reclength is the reclength WITH
corrections. However, as longer as I think about the MyISAM driver as
more obvious is the question, what "pack" means exactly. Does it
really mean compression or only the way of representing (uncompressed)
the data in main memory?
All the best,
Hagen
- --
- ------------------------------------------------------------
Dr.-Ing. Hagen Höpfner | hoepfner@stripped | +49 7251 700 239
- ------------------------------------------------------------
http://www.i-u.de/schools/hopfner/index.html
International University in Germany
School of Information Technology
Campus 3 D-76646 Bruchsal
- ------------------------------------------------------------
Information about the German textbook on "Mobile Databases
and Information Systems" by H. Höpfner, C. Türker and
B. König-Ries are available at http://www.dpunkt.de/.
- ------------------------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
Comment: GnuPT 2.6.0 by EQUIPMENTE.DE
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFD+GOsataeEpWdQtYRAtosAKCaXhjalvYJwMwGXnbOiIZaKHYBogCgqlhL
L/TL5KRVf0QImEnG/SNU5wE=
=dJin
-----END PGP SIGNATURE-----
