mysql - Does this case call for InnoDB or MyISAM? -


I'm doing something searching on a table (gets some input), which is maximum 5 seconds (7.5 million lines). This is a MyISAM table and I am not using full-text indexing on it because I did not make any difference in the speed of use of matches in this case and in this case what is the use of a general "choice" statement? Can see

Now I am "suffering" from closed tables and I am facing questions running for a few minutes after its completion.

Will they have to try to convert the engine to InDebbi? Or do I need to insert or update rows only? This whole table-locking thing is busy grinding my balls ...

row-level and insert And table-level locking is only important for updated queries. If you mostly make the selection (hence not included often to lock the insert / update table) the difference will not be so high (even if the recent standards have done better than Mysam.)

Other ways you might think that the restructuring of your data structure, perhaps an additional lookup table with 'tags' or 'keywords', is a more efficient full-text engine suggested by WebDostroy To Aryanvit.

Last but not least, I wonder if you will get the full text vs. similar results. It may be that if you are searching, if you are not really wide, then in this case maybe a B- Tree index search = enough?


Comments

Popular posts from this blog

c# - sqlDecimal to decimal clr stored procedure Unable to cast object of type 'System.Data.SqlTypes.SqlDecimal' to type 'System.IConvertible' -

Calling GetGUIThreadInfo from Outlook VBA -

Obfuscating Python code? -