InnoDB: Completed initialization of buffer pool InnoDB: Error: checksum mismatch in data file ./ibdata1

untuk menangani:

131104 11:17:16 InnoDB: Completed initialization of buffer pool InnoDB: Error: checksum mismatch in data file ./ibdata1 131104 11:17:16 InnoDB: Could not open or create data files

maka dilakukan

mysqld_safe  --innodb_force_recovery 4

diambil dari 

http://lifeandshell.com/mysql-innodb-error-checksum-mismatch/

rapalan mysql akbar :D

mysqlcheck --all-databases -r #repair
mysqlcheck --all-databases -a #analyze
mysqlcheck --all-databases -o #optimize

Simple Search Engine

http://pctechtips.org/a-simple-php-search-engine-tutorial/
http://onlamp.com/pub/a/php/2002/10/24/simplesearchengine.html?page=3

Removing MySQL from OSX Lion

Removing MySQL from OSX Lion

Recently I've had to remove a version of MySQL 5.5 from my Macbook so that I could go back to a 5.1 version. However it appears that there isn't an automatic way to remove and install an older version. A few google searches revealed a bulk of the removal process, but additional searching revealed a few more steps.

sudo rm /usr/local/mysql
sudo rm -rf /usr/local/mysql*
sudo rm -rf /Library/StartupItems/MySQLCOM
sudo rm -rf /Library/PreferencePanes/My*
rm -rf ~/Library/PreferencePanes/My*
sudo rm -rf /Library/Receipts/mysql*
sudo rm -rf /Library/Receipts/MySQL*
sudo rm -rf /var/db/receipts/com.mysql.*
vim /etc/hostconfig # and remove the line MYSQLCOM=-YES-

9/28/2011 - added comment on last line. Thanks Justin for pointing this out! 

Web references:

• http://stackoverflow.com/questions/1436425/how-do-you-uninstall-mysql-from-mac-os-x
• http://akrabat.com/computing/uninstalling-mysql-on-mac-os-x-leopard/

taken from: http://johnmcostaiii.net/2011/removing-mysql-osx-lion/

don't create dynamic tables

Image via Wikipedia

If you are creating a table dynamically, that most likely means you do not understand relational database ideology and as a result doing something wrong.
Just create all the tables at application setup from ready made dump and do not create any tables at runtime.
No need to use dynamic table name at all.
taken from:
http://stackoverflow.com/questions/3665784/php-pdo-prepared-statements-dont-work-when-creating-a-table

Related articles

• SQLiteDatabase: Create multiple tables dynamically at runtime? (stackoverflow.com)
• Map multiple tables to a single entity dynamically (stackoverflow.com)

catatan dari http://dev.mysql.com/doc/refman/5.1/en/multiple-servers.html

The warning against sharing a data directory among servers also applies in an NFS environment. Allowing multiple MySQL servers to access a common data directory over NFS is a very bad idea.

• The primary problem is that NFS is the speed bottleneck. It is not meant for such use.

• Another risk with NFS is that you must devise a way to ensure that two or more servers do not interfere with each other. Usually NFS file locking is handled by the lockd daemon, but at the moment there is no platform that performs locking 100% reliably in every situation.

Make it easy for yourself: Forget about sharing a data directory among servers over NFS. A better solution is to have one computer that contains several CPUs and use an operating system that handles threads efficiently.