Search Results
Search type | Search syntax |
---|---|
Tags | [tag] |
Exact | "words here" |
Author |
user:1234 user:me (yours) |
Score |
score:3 (3+) score:0 (none) |
Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
Views | views:250 |
Code | code:"if (foo != bar)" |
Sections |
title:apples body:"apples oranges" |
URL | url:"*.example.com" |
Saves | in:saves |
Status |
closed:yes duplicate:no migrated:no wiki:no |
Types |
is:question is:answer |
Exclude |
-[tag] -apples |
For more details on advanced search visit our help page |
This tag is ambiguous. For database tables, use "database", for html tables use "template" or "html", for shipping table rates use "table-rates"
0
votes
2
answers
1k
views
Troubleshooting "Base table or view not found"
I don't know why mm is being referenced as a table and do not see it declared as a table in any of our modules. … SQLSTATE[42S02]: Base table or view not found: 1146 Table 'magento_db.mm' doesn't exist, query was: UPDATE `mg_core_config_data` SET `scope` = ?, `scope_id` = ?, `path` = ?, `value` = ? …
16
votes
3
answers
7k
views
Some Magento tables are not InnoDB, is it safe to convert all tables to InnoDB?
For me this returned mostly temporary index tables and magento module tables, so not a lot of critical core tables to be concerned about and few enough tables that I can easily execute another alter table … For each table returned I executed: Alter table {table-name} ENGINE=InnoDB;
I'd be nervous to try this if none of your tables are InnoDB. …