mysql >=4.1 required (Bugs)

by done @, Wednesday, March 07, 2007, 19:44 (4554 days ago)
edited by done, Wednesday, March 07, 2007, 22:40

I just wanted to remark that mlf2beta5 doesn't work with mysql-versions below 4.1, because of a different timestamp format.
furthermore the collate specification used in initial.sql (utf8_bin) doesn't seem to work with older mysql-releases either.
perhaps you should notice this in your documentation.

I think, it would be best to use unix-timestamps to garantuee compatibility.
what exactly are the advantages of utf8_bin compared to utf8_general/_unicode?
why not use utf8_general_ci (default setting)?

Avatar

mysql >=4.1 required

by Alex ⌂ @, Thursday, March 08, 2007, 19:50 (4553 days ago) @ done

Hi,

I think, it would be best to use unix-timestamps to garantuee
compatibility.

Hm..., the manual says: "TIMESTAMP columns are displayed in the same format as DATETIME columns. In other words, the display width is fixed at 19 characters, and the format is YYYY-MM-DD HH:MM:SS."

why not use utf8_general_ci (default setting)?

You're right, it should be utf8_general_ci.

mysql >=4.1 required

by done @, Friday, March 09, 2007, 11:31 (4552 days ago) @ Alex
edited by done, Friday, March 09, 2007, 12:42

I think, it would be best to use unix-timestamps to garantuee
compatibility.

Hm..., the manual says: "TIMESTAMP columns are displayed in the same
format as DATETIME columns. In other words, the display width is fixed at
19 characters, and the format is YYYY-MM-DD HH:MM:SS."

the manual also says: "From MySQL 4.1.0 on, TIMESTAMP display format differs from that of earlier MySQL releases". (http://dev.mysql.com/doc/refman/4.1/en/timestamp-4-1.html)
the format used to be YYYYMMDDHHMMSS in releases below 4.1.
however, that wasn't the problem.
I had to set CURRENT_TIMESTAMP in qotes.

RSS Feed of thread
powered by my little forum