RISK - BANG IT!!

"A leader would give birth to another leader only if he is willing to give the driving seat, and is also prepared if the choice fails." It was a simple management lesson for creating leaders. It is very different from a simple delegation. Delegating creates only subordinates, leadership creates superiors and differentiators.

        However, the only careful planning that one needs to do is, to choose the 'Right Driver'. After that, just hand over the keys to the driver and stand by him. Even if the driver bangs the BMW, or ruins a budget exercise or a planning, stand by him. The primary responsibility of the failure is not the driver.

       The potential of a hidden human talent would be coming out colorfully only when we open the lid. Invariably, the lid is there in each one of us, but opportunities should be created to open the lid. I also realized that the willingness to give the driver's seat alone is not sufficient, but it also requires the talent to choose the right driver and we need to invest time and energy to guide the driver without holding the steering. One need to have a threshold of a risk. Taking a chance is by choice and not by chance.

       Find the new driver, you can buy a new car. Get a new leader, you can create a new business - "thok do"

Overwrite MySQL Error Messages

Well, in the current project where I am responsible to migrate SQL Server 2005 to MySQL 5.x database, I've found an interesting use case. The application development team expects the custom alert messages to be sent from the MySQL database(This is handled by using the raiseerror keyword in SQL Server 2005). In order to approach this problem, I've investigated couple of ways out of which one turned out to be as a solution: customizing the default MySQL error messages.

P.S: This is currently working ONLY on WINDOWS platform

Procedure:

1. Explore through /share/errmsg.txt
2. Edit the required error text. For example: ER_PARSE_ERROR & ER_SYNTAX_ERROR (in my scneario)
3. In the command prompt,navigate through /bin
4. Execute the following command: comp-err --charset=../share/charsets --in_file=../share/errmsg.txt --out_dir=../share
5. Restart MySQL service.

Good Luck!!

Uninstall MySQL from Mac OSX

Perform the following operations from terminal:

1. sudo rm /usr/local/mysql
2. sudo rm -rf /usr/local/mysql*
3. sudo rm -rf /Library/StartupItems/MySQLCOM
4. sudo rm -rf /Library/PreformancPanes/My*
5. (Edit /etc/hostconfig) sudo vi /etc/hostconfig (Remove line MYSQLCOM=-YES)
6. sudo rm -rf /Library/Reciepts/mysql*
7. sudo rm -rf /Library/Reciepts/MySQL* 

MySQL Error 126: Incorrect key file for table '/tmp/#sql_30fc_0.MYI'

This bug has irritated me big time. Upon further observation, I determined that the error I got was the result of temporary table getting very large.
Please check the disk space (command: df -h) and make sure you have enough space.

This resolves the problem!!