Last night, finally i’ve cut my hair that i’ve kept for long time, with new life, new direction, new vision, everything new
New hairstyle, new life
New syntax for new MySQL
Downloaded new version of MySQL database, version 4.1.12. Just like usual, many new features.
When I execute my old PHP programs (version 4), there is an error occured that I can’t connect to my new MySQL database — old password is not usable.
After searched the net, found few ways to overcome this as shown at http://dev.mysql.com/doc/mysql/en/old-client.html
So I have to reset the password at MySQL Command Line Client so that my old PHP program can connect to the database, and it works.
If using PHP version 5, there is a new extension to connect to MySQL version 4.1 and above, that is mysqli (short of MySQL Improved), documentation at http://php.net/mysqli. So in future we need to work with database using these commands like mysqli_connect(), mysqli_fetch_array()…
So should we migrate to PHP5 if using MySQL 4.1 above, or still stick with old MySQL and old PHP4? (since most of the hosting company still having old installation)
Unpleasant experience with VB.Net 2005 Beta
Been using VB.NET 2005 Beta for 1 week plus, at first was amazed with the speed and intelligent of VB.Net 2005 that can bring, however after some time, some problems rose. At first it can’t open the design view of projects created in version 2002 and converted to version 2005 once. Then I have to redesign the interface of every form then it works again.
Now after a system crash, it can’t even open up any project (vbproj) and solution (sln) files. And one more thing I noticed is, there is a process named ‘mscorsvw.exe’ in my Task Manager consumes average 85 - 99% of CPU usage which is slows down the performance of whole PC.
I solved all the problem uninstalling VB.Net 2005 and .Net Framework v2.0 then everything is back to normal. But the problem is, I had my project developed with version 2005, I can’t reopen those projects under version 2002… O_O
Hope these problems only in Beta version of VB.Net 2005, else it will be big problem for both developer and Microsoft too.





