> > > As you have noticed - you cannot.
> > >
> > > So, all you can do is creating a MyISAM table and copying
> > > the column contents.
> > Are you suggesting to have a full copy of the table in MyISAM format?
> No, only the BLOB/TEXT columns need to be moved to MyISAM.
> > Is there any other workaround? The reason because we are using InnoDB is
> > because there s full support
> > - for foreign keys,
> > - for joint queries
> > - for rollback on commit
> The MyISAM table type also fully supports JOIN queries. More importantly,
> for you, it supports full-text indexes.
> What many people have done to solve the problem you present has been to
> split the original table into two pieces. All BLOB/TEXT fields and a
> field ID are moved to a MyISAM table while the other fields stay in your
> original InnoDB table. This has a distinct performance advantage, too.
> If you run a query that retrieves only non-(BLOB/TEXT) fields from a table
> that has BLOB/TEXT columns defined (any table type), then all of the
> BLOB/TEXT data is read with the rest of the row data off of the disk into
> memory for every row not eliminated by an index, just to be ignored for
> the final output.
Then again - this particular problem is more a MySQL internal
problem that simply should be fixed :-)
Database Workbench - developer tool for InterBase, Firebird, MySQL & MS SQL