| List: | General Discussion | « Previous MessageNext Message » | |
| From: | symbulos partners | Date: | January 28 2005 4:14pm |
| Subject: | Re: FULLTEXT index on InnoDB tables (looking for a workaround) | ||
| View as plain text | |||
On Friday 28 Jan 2005 15:41, you wrote: > 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? 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 Does anybody know any other way of indexing the table in a way, which would allow full text search? -- symbulos partners -.- symbulos - ethical services for your organisation http://www.symbulos.com
| Thread | ||
|---|---|---|
| • FULLTEXT index on InnoDB tables | symbulos partners | 28 Jan |
| • Re: FULLTEXT index on InnoDB tables | Martijn Tonies | 28 Jan |
| • Re: FULLTEXT index on InnoDB tables (looking for a workaround) | symbulos partners | 28 Jan |
| • Re: FULLTEXT index on InnoDB tables (looking for a workaround) | SGreen | 28 Jan |
| • Re: FULLTEXT index on InnoDB tables (looking for a workaround) | Martijn Tonies | 28 Jan |
| • Re: FULLTEXT index on InnoDB tables (looking for a workaround) | symbulos partners | 28 Jan |
| • Re: FULLTEXT index on InnoDB tables (looking for a workaround) | Sasha Pachev | 28 Jan |
| • Re: FULLTEXT index on InnoDB tables (looking for a workaround) | mos | 30 Jan |
| • Re: FULLTEXT index on InnoDB tables (looking for a workaround) | corradoerina@btopenworld.com | 28 Jan |
| • Re: FULLTEXT index on InnoDB tables (looking for a workaround) | Nick Arnett | 28 Jan |
| • Re: FULLTEXT index on InnoDB tables (looking for a workaround) | Heikki Tuuri | 30 Jan |
