Peter Zaitsev wrote:
Hi,
One of approaches is to have "shadow" MyISAM table in addition to your
Innodb table to perform full text search, which you can update in bulks
or via triggers.
How can I ensure isolation for queries on this "shadow" table? The
documentation says that the table type does not support transactions.
Sorry for being a bit dense here, but what do you mean exactly? Will
updates to the "shadow" table only be visible in their own transaction
until commit? Will they be rolled back on transaction abort?
You also can try sphinx: http://www.sphinxsearch.com/ which works with
any storage engine and also much faster.
From what I can tell from the Sphinx docs, it is not transactional
either. Not only that, it does not support SQL tables at all, it is
simply a wrapper for a search API using the mysql storage engine
interface. Can you please elaborate on what you mean?
Thanks,
LL
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
