Hi, We would like to upgrade our current installation of Mysql 4.0.x to 4.1 to be able to switch fastly to the MySQL Cluster Solution. The problem is, that we were using the TIMESTAMP type quite heavily in the SELECTS, and we splitted the result using for example, substring in php, so we assume that position 4 to 6 is the month and so on. Now with the new structure of TIMESTAMP, all these functions fail.
I had a look at several ways to get out there, but each solution was to change the queries itself. The SELECT timestamp+0 seemed to be the easiest one, does this "hack" work forever in any forthcomming versions? The problem of this is that it will take several month to do so, we have over 100.000 queries in over 5.000 files together with a lot of scripts on external servers. This step certainly has to be made some time, but we would like to do it over a certain period of time, where we could already using the cluster, which is really important for us to have as soon as possible. I read that 4.0 could be run in new mode (--new), where it already outputs the TIMESTAMP using the new representation. Is there nobody who has a similar solution to force 4.1 to act as a 4.0 regarding TIMESTAMP output ? This would be, for us, the best solution to change all the queries one by one, being able to test it on a 4.1 system, and to gain some time to do so while running on the clustered system. Any Help would be very appreciated. Many Thanks & Best Regards, Tom Weber -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
