My question is two-fold, first regarding error handing of table size
limitations, and secondly performance and other implications of raid
striping.
I'm building a system with an integrated MySQL database and there is a
potential for filling up tables to the maximum file size for the OS I&#x
On Wednesday 15 August 2001 11:30, Dan Nelson wrote:
> In the last episode (Aug 15), Nathanial Hendler said:
> > I have a table that holds a lot of information. I tried to INSERT
> > something into it, and received...
> >
> > DBD::mysql::st execute failed: The table 'fancy_big_table' is full at
>
In the last episode (Aug 15), Nathanial Hendler said:
> I have a table that holds a lot of information. I tried to INSERT
> something into it, and received...
>
> DBD::mysql::st execute failed: The table 'fancy_big_table' is full at
> ./tom_to_mutt.pl line 156.
>
> The table is 4G is size. Th
Look into MAX_ROWS... ie:
alter table mytable max_rows = 1
ryan
- Original Message -
From: "Nathanial Hendler" <[EMAIL PROTECTED]>
To: "MySQL" <[EMAIL PROTECTED]>
Sent: Wednesday, August 15, 2001 12:19 PM
Subject: Table size limitations...
>
this value.
Hope this helps, here's a pointer to more information on this:
http://www.mysql.com/documentation/mysql/bychapter/manual_Introduction.html#
Table_size
- Trevor
-Original Message-
From: Nathanial Hendler [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 15, 2001 10:20 AM
T
I have a table that holds a lot of information. I tried to INSERT something
into it, and received...
DBD::mysql::st execute failed: The table 'fancy_big_table' is full at
./tom_to_mutt.pl line 156.
The table is 4G is size. The table's Max_data_length = 4294967295 (4G)
I'm running the MySQL
