1. MySQL : failed to start, complaining about:
   PLAIN TEXT
   CODE:

   1. /etc/init.d/mysql: ERROR: Using expire_logs_days without log_bin crashes
   2. the server. See README.Debian.gz

   Commenting out the expire_logs_days in the my.cnf file allowed me to restart MySQL.

2. After the upgrade of Apache, my virtual hosts weren't working. A quick search via Google pointed me to this post - a quick edit of all of my host files and it was all working again.
3. the php-mysql connector somehow hadn't been upgraded/installed so a quick
   PLAIN TEXT
   CODE:

   1. apt-get install php5-mysql

   fixed that problem.

4. OpenBD : the only thing that remains broken was my tomcat5.5 Open BD install. Tomcat was working fine but Open BD refused to start up complaining about :
   PLAIN TEXT
   CODE:

   1. javax.servlet.ServletException: Open BlueDragon Engine Failed to initialise tags: java.awt.Color

   Since I am not really using it, it's not that important, but at some stage I'd like to get it working again. If you have any suggestions, please leave a comment.

UPDATE

In a similar vein, Nadav Samet covers off in more detail Cross Site Scripting attacks, how they work and what you can do to protect your site.

UPDATE

I have also recently found out that the following works just as well:

Installing MyODBC is straightforward. Unzip the downloaded file and click on the setup.exe file and simply follow the installation prompts. For starters just keep accepting the default settings if you are unsure of any options.

OK, now we are ready to add a MySQL datasource. You have to do this through ODBC datasources in the Control Panel. Please note: if you were planning on using the Cold Fusion Administrator, you can't. You have to go through the Control Panel to initially configure the datasource. Once setup you can modify your MySQL datasources through the Cold Fusion Administrator. So go ahead and fire up your ODBC manager.

Once open, go to the the system DNS tab and select Add.... From the list of available drivers select MySQL and click Finish. This should fire up a dialogue with a whole bunch of fields. Listed below is a sample entry:

Things to bear in mind are: from my personal experience, I found that it's best to keep windows DSN and database name in lower case. Specifying the IP address works, I have had problems using the host name setting. As for the username and password, make sure that you use those properties that you set to the database you created. I.e. if you don't require a logon to connect to that database, then leave the fields blank. Else enter the username and password assigned to that database (the default root account will work well, but is contentious for security reasons).

Well we are done you should know have configured your system to connect to a MySQL database via ODBC.

OK so far so good. Now you will need to setup MySQL to run as a service. This is easy just switch to c:\mysql\bin. There you will see a file called mysqld-nt.exe. This is the file that installs MySQL as a service on your NT box. You install the service with the following command:

After a couple of seconds (or less depending on the speed of your machine) the service is installed and you can test the installation (it doesn't tell you if the service has been successfully installed or not) by typing: net start MySQL (incidentally should you wish to stop the server just type net stop MySQL). NT should inform you that the service is starting and whether it has started successfully or not.

On to the next stage. We will now secure the database server a little bit. As per the default installation the Administrator username is root and it has no password set. As you can imagine this is a serious security hazard. So in the following we are going to reset the password, by logging into MySQL (specifically the system database mysql) and removing the default user account, exiting the server reloading it and re-setting the password for root. Simply type the commands in listed below (you can read through the documentation on this subject at http://127.0.0.1/{your SQL documentation mapping}/manual.html#Win32, section 4.12.4):

Next we will test whether your changes were successful, try login back into the database server, from the command prompt type mysql -u root -p mysql this should prompt you for a password. Type in the password you have just specified and you be logged in. Don't log out because we are now going to create another database. The steps syntax is very simple for this. From the MySQL command prompt type: create database <your database name> ;. Now type show databases; and this should provide you with a list of databases available.

Well there you go. You know should be able to install, configure, secure and create a database in MySQL. In the coming days I will try and write up something about installing MyODBC so that you can get other applications (such as Cold Fusion) to talk to MySQL. I hope you found this article useful!

Listed in this document will be a collection of problems I encountered while working with both Cold Fusion and MySQL, and some of the work arounds/solutions I have come across to resolve these problems.

• When planning to store and display large amounts of data in a text field, you have to be aware of a setting in the Cold Fusion Administrator. By default the Long Text Buffer Size is limited to 65,000 characters. As a result should you have more than 65,000 characters to display the excess will be chopped. This problem can be fixed by either increasing the Long Text Buffer Size (better for performance, but still has an impact) or by enabling Long Text Retrieval Settings (can have an impact on performance). These settings can be reached by editing the datasource properties.