Hi Jigal and thank you,
I have been lucky and got almost all tables working just ok, only the 3
sites left.
10.8.2011 0:34, Jigal van Hemert kirjoitti:
If it's a cache table, do a truncate before converting it, or drop it
first and create it new.
The tables are mainly cache tables, those tha
Hi,
On 9-8-2011 19:29, Katja Lampela wrote:
ok more info; in one of these only-myISAM-sites (that I want to change
back to InnoDB) the phpmyadmin shows in Structure tab the cache tables,
but in their column (combined columns Records, Type, Collation, Size and
Overhead) there is only this text: "
Hi,
4.8.2011 11:00, Katja Lampela kirjoitti:
CREATE TABLE cache_hash ( id int(11) unsigned NOT NULL auto_increment,
hash varchar(32) NOT NULL default '', content mediumblob, tstamp int(11)
unsigned NOT NULL default '0', ident varchar(32) NOT NULL default '',
PRIMARY KEY (id), KEY hash (hash) ) E
Hi,
And thanks, but this myisamchk didn't help here.
4.8.2011 16:23, Mathias Schreiber [wmdb] kirjoitti:
So any idea, what should I do now? If you think this is a bigger issue
and fixing it needs some financing, please contact me by email.
I'd go and run myisamchk first.
Maybe just some inde
hi,
ok more info; in one of these only-myISAM-sites (that I want to change back to InnoDB)
the phpmyadmin shows in Structure tab the cache tables, but in their column (combined
columns Records, Type, Collation, Size and Overhead) there is only this text: "in
use".
Other sites don't give this.
Hi,
The situation at the moment with some big databases following - I use the
cache_hash table as example.
The install tool tells me to create the cache tables, like:
CREATE TABLE cache_hash ( id int(11) unsigned NOT NULL auto_increment, hash
varchar(32) NOT NULL default '', content mediumblob
So any idea, what should I do now? If you think this is a bigger issue
and fixing it needs some financing, please contact me by email.
I'd go and run myisamchk first.
Maybe just some index got messed up.
--
Ernesto, Nov. 9th 2010:
"In the graphics generation routines of TYPO3 *anything* cou
Hi,
I've been struggling now with innoDB's configuration on a virtual hosting
server.
Now the innoDB was configured poorly and the ibdata1 file raised up to
enourmous size.
For solution I installed to TYPO3installations the extension ggforcemyisam that
forces MyISAM tables in TYPO3 installat
