There is an issue in ISAM/MyISAM tables of needing to have correctly sized row pointers. I submitted this as a bug report (it's really a documentation bug), but don't know if it will be fixed. I was happy to get an answer, though, so will share it with you :-)
If you get an error like this: "ERROR 1030: Got error 136 from table handler." Try: ALTER TABLE tablename MAX_ROWS=[very large value]; INNODB tables do not have the same limitation. I do not know about BDB tables. My large table: mysql> select count(*) from inv0web02; +-----------+ | count(*) | +-----------+ | 498093481 | +-----------+ -- Greg On Mon, Jan 19, 2004 at 11:24:19AM -0800, Daevid Vincent wrote: > mysql> select count(*) from atoms_in_universe; > +-------------------------+ > | count(*) | > +-------------------------+ > | 30204541410292874012341 | > +-------------------------+ > 1 row in set (0.07 sec) > > Daevid Vincent > http://daevid.com > > > > -----Original Message----- > > From: Will Lowe [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, December 23, 2003 8:38 PM > > To: Andrew Braithwaite > > Cc: 'Paul DuBois'; 'Andres Montiel'; '[EMAIL PROTECTED]' > > Subject: Re: 100,000,000 row limit? > > > > > I don't believe this. I'm going to write a script to > > disprove this theory > > > right now.. > > > > We have a lot more than 100,000,000 more than that in a single MyISAM > > table at work: > > > > mysql> select count(*) from probe_result; > > +-----------+ > > | count(*) | > > +-----------+ > > | 302045414 | > > +-----------+ > > 1 row in set (0.00 sec) > > > > -- > > thanks, > > > > Will Dr. Gregory B. Newby, Research Faculty, Arctic Region Supercomputing Center University of Alaska Fairbanks. PO Box 756020, Fairbanks, AK 99775 e: newby AT arsc.edu v: 907-474-7160 f: 907-474-5494 w: www.arsc.edu/~newby -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
