Skip to content
This repository has been archived by the owner on Feb 3, 2022. It is now read-only.

Triggers in enterprise cause tables to be read only #28

Closed
brideo opened this issue Jan 18, 2016 · 1 comment
Closed

Triggers in enterprise cause tables to be read only #28

brideo opened this issue Jan 18, 2016 · 1 comment
Assignees

Comments

@brideo
Copy link

brideo commented Jan 18, 2016

Because the trigger is created by a certain user on the production/downloaded environment, we can not edit that table on our local environment unless we have that user.

n98 Magerun get around this issue by stripping out this command on export:

mysqldump --single-transaction --quick -h'localhost' -u'db_user' -p'db_password' 'db_name' | sed -e 's/DEFINER[ ]*=[ ]*[^*]*\*/\*/' > 'export_name.sql';

@tgerulaitis
Copy link
Member

Good catch! This explains why we didn't encounter this issue until we started using magedbm.

@bobbyshaw bobbyshaw self-assigned this Mar 14, 2016
bobbyshaw added a commit that referenced this issue Mar 16, 2016
Fixes #28: Skip triggers when dumping database.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants