Atomic Corp + Magento + php-mcrypt x64

Magento
Atomic Corp's rpm repository

wget -q -O - http://www.atomicorp.com/installers/atomic | sh

yum install php-mcrypt.x86_64

Importing HUGE databases

Assumptions:

1. Huge means over 1GB or possibly 1TB (not tested) on MySQL.

2. This means that using tools like PhpMyAdmin, etc are not feasible (timeout, php.ini constraints, etc)

Problems:

1. MySQL dumps are NOT done in order of table dependencies. So it is highly possible that your dependent child table is created before the parent table is created in the SQL script. This is especially more so if you have a lot of tables in the database.

Solution:

1. Need to disable the foreign key constraint checks.

Constraint:

1. You can open up a 1GB file for editing, unless you have uber cool tools like UltraEdit on a Windows machine (almost nothing else works - vim in cygwin, vim in *nix, I dunno but please correct if I'm wrong).

Reference:

http://dev.mysql.com/doc/refman/5.1/en/innodb-foreign-key-constraints.html

How?

mysql> SET foreign_key_checks = 0; 

mysql> SOURCE dump_file_name; 

mysql> SET foreign_key_checks = 1;

That's it, more or less.

Resetting MySQL password on Win 7

1. You MUST (ie. MUST MUST MUST MUST MUST) start the command prompt with "Run as Administrator"!

2. Then you can follow the instructions at:

http://dev.mysql.com/doc/refman/5.1/en/resetting-permissions.html

If you do not start as Administrator, your "user" (even if he has Administrator rights) will not be able to access MySQL binary and data path. It will create a new instance of the database somewhere in

C:\Users\MySuperDuperUselessAdminUser\AppData\Local\VirtualStore\ProgramData\MySQL\blah blah blah...

And this is wrong. Even if you reset the password here, when you start the actual instance via Windows Service, it will go back to the actual datastore location and you will still fail to login.

Yes, it took me 1hour+ to get this sorted out. Hope this saves someone some pain.

GRR...