Yellow Swordfish said:
no connection between the show tables query and the notices and warnings…
As soon as I have code for the options table ‘show’ query I will let you have it.
Thank you! I guess the query being in the same file is indeed just a coincidence then.
As to innoDB tables then the only negative I am aware of is that at one point they did not support FULL TEXT indexing which SP makes use of on the sfposts table.
According to my server guy, apparently innodb still does not support full-text search.
InnoDB uses row-level rather than table-level locking. If a row is being inserted, updated or deleted, only changes to the same row are held up until that request has completed. Tables that receive more updates than selects may be faster with InnoDB.
With this being the case, might a user benefit by converting all SF tables except sfposts to InnoDB? Is that the only table using FULLTEXT? Steve?