I apologize for my skepticism of 15 minutes ago. I finally _read_
http://dev.mysql.com/doc/mysql/en/Table_size.html carefully, and indeed
your suggestion is dead on.
thank you again.
On Mon, 2004-07-26 at 14:19, Paul DuBois wrote:
> At 12:48 -0400 7/26/04, Michael Dykman wrote:
> >I am using a d
thank you for the suggestion, I will give that a try. I thought it
suspicious that the table stopped receiving data at 2 bytes under the
natural 4G limit (8 byte int) which was standard under 3.22. As I said,
I am using a development release and I have found 1 or 2 other
regression errors along t
At 12:48 -0400 7/26/04, Michael Dykman wrote:
I am using a development build of 4.1.3 (the last 4.1.3 release I think;
mysql-4.1.3-beta-nightly-20040628) so I suppose I have this coming, but
here goes:
As I am running on RH Enterprise Server 3 with a Pentium Xeon (32-bit)
According to the documenta
You must be getting an error code when inserting now.
If that is related to index file size (that's what I had)
.
You can do ALTER TABLE MAX_ROWS=
On Mon, 2004-07-26 at 11:48, Michael Dykman wrote:
> I am using a development build of 4.1.3 (the last 4.1.3 release I think;
> mysql-4.1.3-beta-nigh
I am using a development build of 4.1.3 (the last 4.1.3 release I think;
mysql-4.1.3-beta-nightly-20040628) so I suppose I have this coming, but
here goes:
As I am running on RH Enterprise Server 3 with a Pentium Xeon (32-bit)
According to the documentation, for a 32 bit processor, I should be abl
