How to fix Magento2 MySQL error message ERROR 1054: 1054: Unknown column 'entity_id' in 'NEW'
I recently upgraded Magento 2.07 to Magento 2.1 and then to 2.1.1 but now I get the MySQL error ERROR 1054: 1054: Unknown column 'entity_id' in 'NEW' any time I try to import a product or update a product attribute.
I can't re-import my DB backup either because MySQL reports errors whilst importing the backup about NEW.entity_id
magento2 database magento-enterprise
asked Sep 4 '16 at 14:52
MalachyMalachy
54648
bumped to the homepage by Community♦ 10 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I recently upgraded Magento 2.07 to Magento 2.1 and then to 2.1.1 but now I get the MySQL error ERROR 1054: 1054: Unknown column 'entity_id' in 'NEW' any time I try to import a product or update a product attribute.
I can't re-import my DB backup either because MySQL reports errors whilst importing the backup about NEW.entity_id
magento2 database magento-enterprise
asked Sep 4 '16 at 14:52
MalachyMalachy
54648
bumped to the homepage by Community♦ 10 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I recently upgraded Magento 2.07 to Magento 2.1 and then to 2.1.1 but now I get the MySQL error ERROR 1054: 1054: Unknown column 'entity_id' in 'NEW' any time I try to import a product or update a product attribute.
I can't re-import my DB backup either because MySQL reports errors whilst importing the backup about NEW.entity_id
magento2 database magento-enterprise
asked Sep 4 '16 at 14:52
MalachyMalachy
54648
I recently upgraded Magento 2.07 to Magento 2.1 and then to 2.1.1 but now I get the MySQL error ERROR 1054: 1054: Unknown column 'entity_id' in 'NEW' any time I try to import a product or update a product attribute.
I can't re-import my DB backup either because MySQL reports errors whilst importing the backup about NEW.entity_id
magento2 database magento-enterprise
magento2 database magento-enterprise
asked Sep 4 '16 at 14:52
MalachyMalachy
54648
asked Sep 4 '16 at 14:52
MalachyMalachy
54648
asked Sep 4 '16 at 14:52
MalachyMalachy
54648
asked Sep 4 '16 at 14:52
MalachyMalachy
54648
asked Sep 4 '16 at 14:52
MalachyMalachy
54648
54648
bumped to the homepage by Community♦ 10 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 10 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Solution
Just toggle your indexer mode from schedule to realtime and then back to schedule. You can use the Magento Admin (System->Index Management) or the command line tool thus:
bin/magento indexer:set-mode realtime
bin/magento indexer:set-mode schedule
As described in the Magento2 documentation.
What's occurring?
The error is due to some tables eg catalog_product_entity_int having triggers on them so that the scheduled indexer knows what to index. The module CatalogStaging (or one of its dependencies) changes a column name in the table from entity_id to row_id but the trigger does not get updated so it still refers to NEW.entity_id when the entity_id column no longer exists.
The triggers are created when the index mode is set to scheduled so this situation may affect any DB of a Magento install that has been set to index on schedule before upgrading to 2.1.
The fix is simple but not obvious : toggle the indexer to realtime (update on save) and then put it back to schedule. This clears the triggers and then recreates them with the correct reference to the updated column name: NEW.row_id in the trigger as now required by the Magento_CatalogStaging module
answered Sep 4 '16 at 14:52
MalachyMalachy
54648
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "479"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e) {
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom)) {
StackExchange.using('gps', function() { StackExchange.gps.track('embedded_signup_form.view', { location: 'question_page' }); });
$window.unbind('scroll', onScroll);
}
};
$window.on('scroll', onScroll);
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f134667%2fhow-to-fix-magento2-mysql-error-message-error-1054-1054-unknown-column-entity%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Solution
Just toggle your indexer mode from schedule to realtime and then back to schedule. You can use the Magento Admin (System->Index Management) or the command line tool thus:
bin/magento indexer:set-mode realtime
bin/magento indexer:set-mode schedule
As described in the Magento2 documentation.
What's occurring?
The error is due to some tables eg catalog_product_entity_int having triggers on them so that the scheduled indexer knows what to index. The module CatalogStaging (or one of its dependencies) changes a column name in the table from entity_id to row_id but the trigger does not get updated so it still refers to NEW.entity_id when the entity_id column no longer exists.
The triggers are created when the index mode is set to scheduled so this situation may affect any DB of a Magento install that has been set to index on schedule before upgrading to 2.1.
The fix is simple but not obvious : toggle the indexer to realtime (update on save) and then put it back to schedule. This clears the triggers and then recreates them with the correct reference to the updated column name: NEW.row_id in the trigger as now required by the Magento_CatalogStaging module
answered Sep 4 '16 at 14:52
MalachyMalachy
54648
add a comment |
Solution
Just toggle your indexer mode from schedule to realtime and then back to schedule. You can use the Magento Admin (System->Index Management) or the command line tool thus:
bin/magento indexer:set-mode realtime
bin/magento indexer:set-mode schedule
As described in the Magento2 documentation.
What's occurring?
The error is due to some tables eg catalog_product_entity_int having triggers on them so that the scheduled indexer knows what to index. The module CatalogStaging (or one of its dependencies) changes a column name in the table from entity_id to row_id but the trigger does not get updated so it still refers to NEW.entity_id when the entity_id column no longer exists.
The triggers are created when the index mode is set to scheduled so this situation may affect any DB of a Magento install that has been set to index on schedule before upgrading to 2.1.
The fix is simple but not obvious : toggle the indexer to realtime (update on save) and then put it back to schedule. This clears the triggers and then recreates them with the correct reference to the updated column name: NEW.row_id in the trigger as now required by the Magento_CatalogStaging module
answered Sep 4 '16 at 14:52
MalachyMalachy
54648
add a comment |
Solution
Just toggle your indexer mode from schedule to realtime and then back to schedule. You can use the Magento Admin (System->Index Management) or the command line tool thus:
bin/magento indexer:set-mode realtime
bin/magento indexer:set-mode schedule
As described in the Magento2 documentation.
What's occurring?
The error is due to some tables eg catalog_product_entity_int having triggers on them so that the scheduled indexer knows what to index. The module CatalogStaging (or one of its dependencies) changes a column name in the table from entity_id to row_id but the trigger does not get updated so it still refers to NEW.entity_id when the entity_id column no longer exists.
The triggers are created when the index mode is set to scheduled so this situation may affect any DB of a Magento install that has been set to index on schedule before upgrading to 2.1.
The fix is simple but not obvious : toggle the indexer to realtime (update on save) and then put it back to schedule. This clears the triggers and then recreates them with the correct reference to the updated column name: NEW.row_id in the trigger as now required by the Magento_CatalogStaging module
answered Sep 4 '16 at 14:52
MalachyMalachy
54648
Solution
Just toggle your indexer mode from schedule to realtime and then back to schedule. You can use the Magento Admin (System->Index Management) or the command line tool thus:
bin/magento indexer:set-mode realtime
bin/magento indexer:set-mode schedule
As described in the Magento2 documentation.
What's occurring?
The error is due to some tables eg catalog_product_entity_int having triggers on them so that the scheduled indexer knows what to index. The module CatalogStaging (or one of its dependencies) changes a column name in the table from entity_id to row_id but the trigger does not get updated so it still refers to NEW.entity_id when the entity_id column no longer exists.
The triggers are created when the index mode is set to scheduled so this situation may affect any DB of a Magento install that has been set to index on schedule before upgrading to 2.1.
The fix is simple but not obvious : toggle the indexer to realtime (update on save) and then put it back to schedule. This clears the triggers and then recreates them with the correct reference to the updated column name: NEW.row_id in the trigger as now required by the Magento_CatalogStaging module
answered Sep 4 '16 at 14:52
MalachyMalachy
54648
edited Sep 4 '16 at 20:33
answered Sep 4 '16 at 14:52
MalachyMalachy
54648
answered Sep 4 '16 at 14:52
MalachyMalachy
54648
answered Sep 4 '16 at 14:52
MalachyMalachy
54648
54648
add a comment |
add a comment |
Thanks for contributing an answer to Magento Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e) {
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom)) {
StackExchange.using('gps', function() { StackExchange.gps.track('embedded_signup_form.view', { location: 'question_page' }); });
$window.unbind('scroll', onScroll);
}
};
$window.on('scroll', onScroll);
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f134667%2fhow-to-fix-magento2-mysql-error-message-error-1054-1054-unknown-column-entity%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e) {
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom)) {
StackExchange.using('gps', function() { StackExchange.gps.track('embedded_signup_form.view', { location: 'question_page' }); });
$window.unbind('scroll', onScroll);
}
};
$window.on('scroll', onScroll);
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e) {
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom)) {
StackExchange.using('gps', function() { StackExchange.gps.track('embedded_signup_form.view', { location: 'question_page' }); });
$window.unbind('scroll', onScroll);
}
};
$window.on('scroll', onScroll);
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e) {
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom)) {
StackExchange.using('gps', function() { StackExchange.gps.track('embedded_signup_form.view', { location: 'question_page' }); });
$window.unbind('scroll', onScroll);
}
};
$window.on('scroll', onScroll);
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
