Skip to main content
10 events
when toggle format what by license comment
Apr 13, 2017 at 12:42 history edited CommunityBot
replaced http://dba.stackexchange.com/ with https://dba.stackexchange.com/
Dec 30, 2014 at 20:59 comment added Mark Doliner It DOES seem weird to import a dump created by MySQL version A into MySQL version B. Dump files usually (always?) contain "DROP TABLE foo; CREATE TABLE foo" Unless someone can cite a reference stating that it's acceptable to alter a table in the mysql database (e.g. maybe MySQL checks the structure of the tables and alters them as needed, if there are missing columns?), then I agree with Rolando that it seems safer to avoid it.
Dec 24, 2012 at 23:30 history edited RolandoMySQLDBA CC BY-SA 3.0
added 5 characters in body
Jun 15, 2012 at 1:35 comment added Aaron Brown Rolando, I have to disagree with you having performed the upgrade dozens of times from 5.1 to 5.5. mysql_upgrade will resolve the discrepancies and the changes are backwards compatible. There is no need to do this.
Jun 14, 2012 at 1:17 vote accept bloudermilk
Jun 13, 2012 at 20:28 comment added RolandoMySQLDBA root@localhost should not have a password upon installation. It should have full privileges already. Just login as follows: mysql -uroot -plocalhost. Once in, run SHOW GRANTS; it should say you have full privs. You will need to assign a password. Just run SET PASSWORD = PASSWORD('myn3wp4$$w0rd');
Jun 13, 2012 at 20:25 comment added bloudermilk This is great! I actually don't care about existing user permissions. How would I do this and just create a new user with full permissions on the new server?
Jun 13, 2012 at 20:19 history edited RolandoMySQLDBA CC BY-SA 3.0
added 373 characters in body
Jun 13, 2012 at 20:07 history edited RolandoMySQLDBA CC BY-SA 3.0
added 3 characters in body
Jun 13, 2012 at 19:47 history answered RolandoMySQLDBA CC BY-SA 3.0