Wednesday 08 October 2003 1:16:08 am
No it's not our code that locks it. The reason for the lock is the behaviour of tables that are of type MyISAM. The table will lock any UPDATEs if a SELECT is running. It can also lock INSERTs in some cases. To avoid this problem you can change the table type of the ezcontentobject (and probably some others that are referred in the search) table to InnoDB, however this probably causes every other operation to be slower. What probably needs to be done is to rethink the search engine, maybe create a new search handler which does things a different way. We also though about having a MySQL specific handler which uses the full text search support in the newer MySQL.
--
Amos
Documentation: http://ez.no/ez_publish/documentation
FAQ: http://ez.no/ez_publish/documentation/faq
|