Remove DEFINER clause from MySQL Dumps

Question

I have a MySQL dump of one of my databases. In it, there are DEFINER clauses which look like,

"DEFINER=`root`@`localhost`"

Namely, these DEFINER clauses are on my CREATE VIEW and CREATE PROCEDURE statements. Is there a way to remove these DEFINER clauses from my dump file?

A bug was reported years ago, but it looks abandoned: https://bugs.mysql.com/bug.php?id=24680 — 1234ru, Sep 27 '19 at 14:32

score 135 · Accepted Answer · edited Nov 17 '14 at 23:34

135

I don't think there is a way to ignore adding DEFINERs to the dump. But there are ways to remove them after the dump file is created.

Open the dump file in a text editor and replace all occurrences of DEFINER=root@localhost with an empty string ""

Edit the dump (or pipe the output) using perl:

perl -p -i.bak -e "s/DEFINER=\`\w.*\`@\`\d[0-3].*[0-3]\`//g" mydatabase.sql

Pipe the output through sed:

mysqldump ... | sed -e 's/DEFINER[ ]*=[ ]*[^*]*\*/\*/' > triggers_backup.sql

edited Nov 17 '14 at 23:34

answered Feb 25 '12 at 19:16

Abhay

6,545
2
22
17

Thanks for the response! So in my text editor, would I replace the entire 'DEFINER=root @ localhost' string with ""? Or replace 'root @ localhost'? – FastTrack Feb 25 '12 at 23:02
1

@FastTrack, please remove the entire string. – Abhay Feb 26 '12 at 07:53
1

What if the dump file is 10G? – bksi Oct 08 '14 at 10:37
Can someone clarify what the sed regex is doing? The one that is posted above as the answer doesn't work for me. I've written my own that does work, but I don't even understand how the one posted above would work. Doesn't 's/DEFINER[ ]*=[ ]*[^*]*\*/\*/', mean match the word DEFINER, followed by 0 or more spaces, followed by =, followed by 0 or more spaces, followed by zero or more characters that are not a literal *, followed by a literal *, and replace it with a literal *? I don't see how that would match DEFINER=`root`@`localhost` – bpeikes Mar 17 '15 at 16:10
@bpeikes, your assessment is right, but this regular expression works on statements like `/*!50017 DEFINER=\`root\`@\`localhost\`*/` and essentially removes the DEFINER statement between asterisks. – sxalexander Apr 06 '15 at 04:49
@sxalexander - so this only works in cases where the "DEFINER" statement is in a comment? – bpeikes Apr 06 '15 at 14:03
@bpeikes as far as I can tell, yes. These worked for my case. – sxalexander Apr 13 '15 at 00:40
8

I suggest to mention that instead of removing the DEFINER it can be set to CURRENT_USER like that: `sed -E 's/DEFINER=`[^`]+`@`[^`]+`/DEFINER=CURRENT_USER/g' dump.sql > new_dump.sql` It has the advantage of keeping restrictions / access control. – 4thfloorstudios Oct 05 '16 at 09:18
on MacOS I'm getting the following error `sed: RE error: illegal byte sequence` – Radu Feb 22 '17 at 17:17
39

The `sed` command does not remove DEFINER clause from procedures and functions. Here is the enhanced version that handles views, triggers, procedures and functions: `sed -e 's/DEFINER[ ]*=[ ]*[^*]*\*/\*/' | sed -e 's/DEFINER[ ]*=[ ]*[^*]*PROCEDURE/PROCEDURE/' | sed -e 's/DEFINER[ ]*=[ ]*[^*]*FUNCTION/FUNCTION/'` – Vladimir Strugatsky Mar 03 '17 at 01:36
if data is dumped and it contains a string with `DEFINER=*`, this will modify the entry. it is unbelievable that mysqldump does not support anything appropriate – phil294 Sep 18 '17 at 08:05
`sed` snippet does not work for procedures. it works for triggers only. – zhekaus Dec 13 '17 at 18:26
6

FYI --- although it was not the case at the time of this answer, MySQL > 5.6 now ships with a mysqldump(1) that supports "--skip-definer" as an option: https://dev.mysql.com/doc/refman/5.7/en/mysqlpump.html#option_mysqlpump_skip-definer – Kevin_Kinsey Aug 14 '18 at 20:53
10

No, it's not mysqldump, but mysql**p**ump who has --skip-definer. – Xdg Jan 05 '19 at 18:39
1

@VladimirStrugatsky's answer is good, I wonder if this might be a bit better way to handle it. `| sed -e 's/DEFINER[ ]*=[ ]*[^*]*\*/\*/; s/DEFINER[ ]*=[ ]*[^*]*PROCEDURE/PROCEDURE/; s/DEFINER[ ]*=[ ]*[^*]*FUNCTION/FUNCTION/` use one pipe and the fact you can string the three sed expressions together rather than three separate pipes. – Sean Oct 29 '19 at 15:42
`sed -e 's/DEFINER[ ]*=[ ]*[^*]*\*/\*/' -e 's/\sDEFINER[ ]*=[ ]*[^* ]*$\s[A-Z]\+\s$/\1/'` – Madacol Feb 18 '20 at 00:04
With mysqldump 10.17 (10.3.23-MariaDB) 'DEFINER' appears twice, so that this simpler plain-text sed match with no regex features works: `sed '/DEFINER \*\/$/d'` – Roger Dueck Sep 25 '20 at 16:20
1

In my case, the perl script didn't find `user`@`localhost`. – Ed Greenberg Sep 01 '21 at 11:01
The example is `DEFINER=root@localhost`, but then the regex in the perl call appears to be looking for an IP address. Am I missing something? – Josh Oct 14 '21 at 14:30

score 104 · Answer 2 · answered Jul 07 '14 at 14:47

104

You can remove using SED

sed -i 's/DEFINER=[^*]*\*/\*/g' mydump.sql

In MacOS:

sed -i '' 's/DEFINER=[^*]*\*/\*/g' mydump.sql

answered Jul 07 '14 at 14:47

Ricardo Martins

5,702
3
40
59

What is going on here in MacOS to be different? – Alex Jan 08 '19 at 13:01
1

The manpage for sed on mac says this: `-i extension` "Edit files in-place, saving backups with the specified extension. If a zero-length extension is given, no backup will be saved. It is not recommended to give a zero-length extension when in-place editing files, as you risk corruption or partial content in situations where disk space is exhausted, etc." – Chad Jan 13 '20 at 22:13
Nice to know that, @Chad. I'm using sed like this in mac for 5+ years now. I never had problems with space or corrupted files. But of course, is something to consider. Thanks for clarifying. – Ricardo Martins Jan 15 '20 at 03:08
I've never run into those issues on Mac either. Just thought I would clarify since @Alex asked :) – Chad Jan 15 '20 at 19:46
it's working fine for me, thanks a lot – TN98 Apr 20 '22 at 08:53

score 76 · Answer 3 · edited Jul 21 '23 at 04:35

76

Since mysql version 5.7.8 you can use the --skip-definer option with mysqlpump (not mysqldump), e.g.:

mysqlpump --skip-definer -h localhost -u user -p yourdatabase

See updated mysql manual at http://dev.mysql.com/doc/refman/5.7/en/mysqlpump.html#option_mysqlpump_skip-definer

edited Jul 21 '23 at 04:35

Raj

22,346
14
99
142

answered Mar 03 '16 at 16:05

maxhb

8,554
9
29
53

17

For whoever wonders what's the difference between `mysqldump` and `mysqlpump` - here is related question: https://dba.stackexchange.com/questions/118846/mysqldump-vs-mysqlpump – Scadge Dec 08 '17 at 14:09
I have phpMyAdmin and MySQL Workbench installed. How do I execute this command on Windows? – posfan12 Jun 28 '18 at 05:29
(after some tests: -1) It uses `information_schema.user`, and this isn't always readable for all users – bato3 Dec 07 '18 at 01:28

score 27 · Answer 4 · edited May 12 '14 at 22:10

I used these ideas to strip the DEFINER clause from my own mysqldump output, but I took a simpler approach:

Just remove the ! before the code and DEFINER, and the rest of the comment becomes a regular comment.

Example:

/*!50017 DEFINER=`user`@`111.22.33.44`*/

is rendered helpless, as little as doing this ..

/* 50017 DEFINER=`user`@`111.22.33.44`*/

The easiest regexp, though, is to remove the ! and the numbers

mysqldump | /usr/bin/perl -pe 's/\!\d+ DEFINER/DEFINER/' > dumpfile.sql

That removes !#### DEFINER and replaces with DEFINER ... you could remove DEFINER too, it doesn't really matter - once the "!" is gone

Awesome and elegant solution! – Wouter Jan 07 '22 at 10:49 — Wouter, Jan 07 '22 at 10:49

score 20 · Answer 5 · answered May 09 '13 at 16:29

20

As per the other's recommendations, here is an example of how to remove the DEFINER from the dump, after the dump has finished:

mysqldump -u user --password='password' -h localhost database | grep -v "50013 DEFINER" > dump.sql

answered May 09 '13 at 16:29

Jonathan

18,229
10
57
56

6

For triggers, the lines look like /*!50003 CREATE*/ /*!50017 DEFINER=`user`@`localhost`*/ /*!50003 trigger my_triggername BEFORE INSERT ON my_table FOR EACH ROW .... */;; and `grep -v` will drop those lines entirely. (although 50017 != 50013) – Kenney Aug 19 '14 at 12:55

score 15 · Answer 6 · answered Jun 22 '15 at 13:18

15

As others mentioned stripping the definer with any kind of regular expression is not too complex. But the other examples stripped the view definitions for me.

This is the regular expression which worked for me:

sed -e 's/DEFINER=[^ ]* / /'

answered Jun 22 '15 at 13:18

Lajos Veres

13,595
7
43
56

1

Doesn't work with triggers - removes also the `*/`. MySQL 5.6.31. – Franc Drobnič Oct 26 '16 at 11:50

score 12 · Answer 7 · answered Mar 25 '14 at 00:52

For an automated solution, you could look at mysqlmigrate. It's a Bash wrapper around mysqldump which allows you to migrate databases and ignore the DEFINER statements. Example:

$ mysqlmigrate -u root -p pass --ignore-definer from_db to_db

http://thesimplesynthesis.com/post/mysqlmigrate (or GitHub)

Otherwise, yes, a command like Abhay points out is needed:

$ mysqldump -u root -ppass the_db | sed -e 's/DEFINER[ ]*=[ ]*[^*]*\*/\*/' > the_db.sql

score 8 · Answer 8 · answered Mar 25 '15 at 20:57

8

You should look the answer here: https://dba.stackexchange.com/questions/9249/how-do-i-change-the-definer-of-a-view-in-mysql/29079#29079

The best way in my opinion to address this problem, is not adding an extra parse of string with sed or grep or any other, instead mysqldump is able to generate a good dump by adding --single-transaction

answered Mar 25 '15 at 20:57

Jose Nobile

3,243
4
23
30

Why downvoted? Why this answer is not considered useful? – Jose Nobile Apr 10 '17 at 21:54
1

Your response still needs about 90 upvotes to get the position it deserves. You have mine :) – Patrick van Bergen Dec 14 '18 at 09:44
I just spent the past 4 hours trying to dump a database. Cant believe it was something so simple! Thanks – A. Fletcher Oct 20 '20 at 16:05

score 6 · Answer 9 · answered Feb 15 '16 at 16:32

6

Another option on OSX to remove definers in-file:

sed -i '' 's/DEFINER=`[^`][^`]*`@`[^`][^`]*`//g' file.sql

answered Feb 15 '16 at 16:32

mohrt

464
5
3

Paul Dixon · Answer 10 · 2013-07-17T14:32:45.270

5

A quick way to do this is to pipe the output of mysqldump through sed to remove the DEFINER statements wrapped in conditional comments. I use this to remove DEFINER from CREATE TRIGGER statements, but you can tweak the condition comment version number in the regex to suit your purposes.

mysqldump -u user --password='password' -h localhost database | \
  sed 's/\/\*!50017 DEFINER=`.*`@`.*`\*\///'

edited Jul 17 '13 at 14:32

answered Jul 17 '13 at 14:09

Paul Dixon

295,876
54
310
348

1

A slightly more readable sed statement: sed "s/DEFINER(.*?)FUNCTION/FUNCTION/" – reustmd Sep 11 '13 at 20:05

score 4 · Answer 11 · answered Jul 22 '14 at 17:44

4

Not sure if it helps but I use SQLyog Community Edition, available at: -

https://code.google.com/p/sqlyog/wiki/Downloads

When dumping sql or copying to another database it allows you to 'Ignore DEFINER'

It is free and provides the basic functionality that a lot of people require

There is also a paid version available from: -

https://www.webyog.com/product/sqlyog

Cheers

answered Jul 22 '14 at 17:44

itfidds

71
1
4

Rather than just flag as 'not useful' perhaps it would be more useful if you reply with why you feel it is not useful? – itfidds Jul 23 '14 at 08:22

score 4 · Answer 12 · answered Oct 05 '20 at 12:25

Best way of dumping and restoring without problems:

MYSQL DUMP

mysqldump -h HOST -u USER -pPASSWORD --single-transaction --quick --skip-lock-tables --triggers --routines --events DATABASE | gzip > "DATABASE.sql.gz" &

MYSQL RESTORE

gunzip DATABASE.sql.gz

sed -i 's/DEFINER=[^ ]* / /' DATABASE.sql
sed -i 's/SET @MYSQLDUMP_TEMP_LOG_BIN = @@SESSION.SQL_LOG_BIN;/ /' DATABASE.sql
sed -i 's/SET @@SESSION.SQL_LOG_BIN= 0;/ /' DATABASE.sql
sed -i 's/SET @@GLOBAL.GTID_PURGED='';/ /' DATABASE.sql
sed -i 's/SET @@SESSION.SQL_LOG_BIN = @MYSQLDUMP_TEMP_LOG_BIN;/ /' DATABASE.sql

mysql -h HOST -u USER -pPASSWORD < DATABASE.sql

For me just the very first `sed` solved the issue. – Lawrence Feb 08 '22 at 18:04 — Lawrence, Feb 08 '22 at 18:04

score 3 · Answer 13 · answered Nov 23 '16 at 19:06

3

For me, this works: perl -p -i.bak -e "s/DEFINER=[^ |\s]*//g" yourdump.dmp. This removed DEFINER=root@localhost from my dump, on each create procedure statment

answered Nov 23 '16 at 19:06

rafwell

429
1
4
12

score 2 · Answer 14 · answered Dec 29 '12 at 08:59

Replace all of your definer users with CURRENT_USER. In my gradle script that creates the backup, my replace script looks like:

ant.replaceregexp(file: "$buildDir/sql/setupDB.sql", match: "`${project.ext.prod_db_username}`@`%`", replace: "CURRENT_USER", byline: true);

which really is just calling ANT. Then you won't have to worry about it.

score 2 · Answer 15 · answered Apr 27 '16 at 10:17

Here is a complete working solution to remove DEFINER information for MySQL 5.6.x and Linux.(Tested on CentOS 6.5).

Usaually we have to replace following entries from Mysql dump(if taken along with data and triggers/routines/functions).

/*!50013 DEFINER=`MYSQLUSER`@`localhost` SQL SECURITY DEFINER */
/*!50013 DEFINER=`MYSQLUSER`@`%` SQL SECURITY DEFINER */
CREATE DEFINER=`MYSQLUSER`@`%` PROCEDURE `PROCEDURENAME`(
CREATE DEFINER=`MYSQLUSER`@`localhost` PROCEDURE `PROCEDURENAME`(
CREATE DEFINER=`MYSQLUSER`@`%` FUNCTION `FUNCTIONNAME`(
CREATE DEFINER=`MYSQLUSER`@`localhost` FUNCTION `FUNCTIONNAME`(
/*!50003 CREATE*/ /*!50017 DEFINER=`MYSQLUSER`@`%`*/ /*!50003 TRIGGER `TRIGGERNAME`
/*!50003 CREATE*/ /*!50017 DEFINER=`MYSQLUSER`@`localhost`*/ /*!50003 TRIGGER `TRIGGERNAME`

The dump was taken with below mysqldump command.

mysqldump -uMYSQLUSER -pPASSWORD DATABASENAME -R > dbdump.sql

The required dump file with no DEFINER information can be obtained with below three commands.

Command-1    
sed -i 's|DEFINER=[^*]*\*|\*|g' [PATH/]dbdump.sql

Command-2
find -name [PATH/]dbdump.sql | xargs perl -pi -e "s/ DEFINER=\`MYSQLUSER\`@\`localhost\`//"

Command-3
find -name [PATH/]dbdump.sql | xargs perl -pi -e "s/ DEFINER=\`MYSQLUSER\`@\`%\`//"

If the dump file is in your current folder then ignore [PATH/].

If data in tables is very huge then take the dump in two files, in one dump file take the dump with data and in other dump file on take the dump of the scripts only (Triggers/Functions/Procedures.) and run the above three commands on 2nd dump(scripts) file.

score 2 · Answer 16 · answered Jan 10 '23 at 16:45

2

if you already exported that sql file, you can change DEFINER inside that file by executing:

sed 's/\sDEFINER=`[^`]*`@`[^`]*`//g' -i your_dumpfile.sql

answered Jan 10 '23 at 16:45

Fiko

21
4

score 1 · Answer 17 · edited Feb 24 '21 at 19:48

On Linux machines you can use this one-liner:

mysql -uuser -ppwd -A --skip-column-names -e"SELECT CONCAT('SHOW CREATE VIEW ',table_schema,'.',table_name,';') FROM information_schema.tables WHERE engine IS NULL and table_schema like 'mydb%'" | mysql -uuser -ppwd -A --skip-column-names | sed -rn 's/.*?VIEW ([^\s]+?) (AS .*?)\s([^\s]+?)\s([^\s]+?)/DROP VIEW \1;\nCREATE VIEW \1 \2;/p' | mysql -uuser -ppwd -A --skip-column-names

You have only to replace strings in bold with your DB user credentials and database name / like pattern.

More info here: https://blog.novoj.net/posts/2014-05-16-recreate-mysql-views-without-definer-one-liner-solution-linux/

score 1 · Answer 18 · answered Jul 23 '14 at 13:31

The only way I could get it working under Windows:

Install http://gnuwin32.sourceforge.net/ to have sed in the command line and add it to the Windows PATH: D:\programs\GetGnuWin32\bin;

sed -i "s|DEFINER=`mydbuser`@`%%` SQL SECURITY DEFINER||g" "D:/prod_structure.sql"

sed -i "s|DEFINER=`mydbuser`@`%%`||g" "D:/prod_structure.sql"

mysqldump -P{port} -h{host} -u{user} -p{password} --routines --no-data --lock-tables=false database_prod > D:\prod_structure.sql

score 1 · Answer 19 · answered Oct 08 '14 at 10:36

Thank you all for the hints. Being lazy, I wrote a script named: "MYsqldump" :

DB=$1
HOST=$2
USER=$3
MYSQLDUMP='/usr/bin/mysqldump'
PARAMS="--complete-insert --disable-keys=0 --extended-insert=0 --routines=0 --skip-comments"
DAY=`date +%d`
MONTH=`date +%m`
YEAR=`date +%Y`
FILE=$DB.$DAY-$MONTH-$YEAR.sql

    if (( $# < 3 )) ; then
        echo ""
        echo "usage: MYsqldump <db> <host> <user>"
        echo ""
        exit 1
    fi

    $MYSQLDUMP -h $HOST -u $USER -p  $PARAMS $DB | grep -v '/*!50013 DEFINER' > $FILE

score 1 · Answer 20 · answered Sep 29 '16 at 00:47

1

For something like:

DELIMITER ;;
CREATE DEFINER=`mydb`@`localhost` FUNCTION `myfunction`() RETURNS int(11)
begin
(...)
end ;;

Try this:

mysqldump --force --routines --opt --user=myuser --databases mydb | sed -e 's/DEFINER=`.*`@`.*`\ //g'

answered Sep 29 '16 at 00:47

impactaweb

11
1

score 1 · Answer 21 · edited Aug 09 '18 at 00:56

1

open your database with any editor, I used with notepad++,
find all test that DEFINER=root@localhost and replace it with nothing("") IE. delete it.

Then you can import it to the any host that you want.

edited Aug 09 '18 at 00:56

Stephen Rauch

47,830
31
106
135

answered Aug 09 '18 at 00:24

Lê Công Danh

11
1

score 1 · Answer 22 · answered Jan 28 '22 at 19:10

As others have said, one possible solution is to replace the usernames in DEFINER clauses to CURRENT_USER.
Note that we must take into account DEFINER in both plain SQL statements and in special comments, like in the following examples:

CREATE DEFINER=`root`@`localhost` FUNCTION...
/*!50013 DEFINER=`MYSQLUSER`@`%` SQL SECURITY DEFINER */
/*!50017 DEFINER=`root`@`localhost`*/

So, for me, what works is this:

mysqldump <my-options> | sed -E 's/DEFINER=[^ *]+/DEFINER=CURRENT_USER/g' > dumpfile.sql

score 0 · Answer 23 · answered Oct 26 '16 at 12:16

The simplest regex that works for me with all objects is:

sed 's/DEFINER=[^ ]*`//' ...

Note that quote-names has to be TRUE (which is by default).

Hope that in newer versions the switch --skip-definer introduced in mysqlpump in version 5.7 comes to mysqldump, too.

score 0 · Answer 24 · answered Apr 23 '18 at 06:56

0

I have used PowerShell script to remove all the lines with DEFINER:

get-content $file_in_full_path | select-string -pattern $line_string_delete -notmatch | Out-File -width 1000000000 -Encoding Default $file_out_full_path

answered Apr 23 '18 at 06:56

Alen

49
5

score 0 · Answer 25 · answered Jan 05 '19 at 19:11

Nothing was working for me, so I needed to write my own regex.

Try to dump your database into file, cat whole file and grep only your definer statements to see them.

cat file.sql | grep -o -E '.{,60}DEFINER.{,60}'
Write your regex
Pipe your dump into sed with this regex. For example mine statement is:

mysqldump | sed -E 's//*!500[0-9][0-9] DEFINER=.+?*///' | sed -E 's/DEFINER=?[^ ]+??@?[^ ]+? ?//'
Profit!

score 0 · Answer 26 · answered Sep 26 '19 at 18:40

0

remove_definers.bat:

@echo off
(for /f "tokens=1,2*" %%a in (dumpfile.sql) do (
 if "%%b"=="" (echo %%a) else (
  echo %%b | find "DEFINER" > null && echo %%a %%c || echo %%a %%b %%c
 )
)) > dumpfile_nodefiners.sql

answered Sep 26 '19 at 18:40

Luiz Rodolfo

1

score 0 · Answer 27 · answered Sep 25 '20 at 16:13

Referring to https://stackoverflow.com/a/19707173/1488762, I suspect the following may perform better on very large databases - modify the definer at the end, rather than performing additional regex processing on every line:

mysqldump myDB > dump.sql
cat >> dump.sql << END
SELECT CONCAT("ALTER DEFINER=`youruser`@`host` VIEW ", 
table_name, " AS ", view_definition, ";") 
FROM information_schema.views 
WHERE table_schema='myDB';
END

score 0 · Answer 28 · answered Oct 05 '20 at 09:38

0

Just for my future reference, sd version.

mysqldump ... | sd 'DEFINER=.*?\*' '*' > file.sql

answered Oct 05 '20 at 09:38

jeiea

1,965
14
24

midlan · Answer 29 · 2021-05-12T16:58:29.650

My solution for removing DEFINER tested on my MariaDB 10.3:

mysqldump | grep -v -P 'SQL SECURITY DEFINER \*/$' | perl -pe 's/(?<=^\/\*!50003 CREATE\*\/ )\/\*!50017 DEFINER=`.+`@`.+`\*\/ (?=\/\*!50003 TRIGGER)//'

grep removes it for views, perl removes it for triggers

This solution is is attacker-proof, because it matches start and end of lines. So even if attacker knows you are doing replace of DEFINER on your dumps, his DEFINER arranged in the data won't be replaced.

score 0 · Answer 30 · answered Jun 19 '21 at 19:47

If your SQL file has DEFINER occurances (with and) without conditional comments, then you might be interested in this alternative REGEXP.

sed -Ei \
    's/DEFINER\s*=\s*(["'\''`]?)[^"'\''`@]+\1\s*@\s*(["'\''`]?)[^"'\''`\*]+\2//g' \
#      [-----1------][----2----][----4----]-5[--6--][----------7------------]
    "$FILE"

Explanation:

DEFINER {potential whitespace} = {potential whitespace} …
… {any potential quote or backtick, captured} …
(break sequence, add escaped single-quote, resume sequence – because we wrap the construct with single-quotes)
… (username) {string: no quote or @} …
… {use first capturing group – the quote – if any} …
… {potential whitespace} @ {potential whitespace} …
… {same for host with new capturing group, but also exclude asterisk}.

(Run without the commented explanation line because that would throw an error)

Remove DEFINER clause from MySQL Dumps

30 Answers30

MYSQL DUMP

MYSQL RESTORE

Linked