UBB.Developers Forums UBB.threads 6 Bug Reports Some timestamp columns too small?

[6.0.1]

w3t_Posts.B_LastEdit, w3t_Online.O_Last, and w3t_Subscribe.S_Last are int9. Should that be int11?

P.S. This reminds me of something I've been curious about. Why are numeric Unix timestamps used, rather than the built-in MySQL date/time column types?

When originally creating the scripts I had thought that the number after the INT was how many places there were, like INT(11) would be an 11 digit integer. Actually it's a lot bigger than that. Even an INT(9) is probably too big. Need to figure out the actual size but haven't had a chance yet.

As for using the builtin mysql date/time columns, I wasn't sure if that was going to be flexible enough when first creating threads.

All INT(X) does is specify how many digits are actually shown. In MySQL, INT is always 4 bytes long, which means that it stores: -2147483648 to 2147483647, or when used with unsigned, 0 to 4294967295.

nice try with the cookie stuff. Luckily it won't work!

Actually, it did work until threadsdev was upgraded to 6.0.2... which is a frightening thought. It was my second (and more complex) example of why html in signatures is bad. You could tell whether that script could read your cookies based on whether you got the grin or frown image back (grin = it could read them, frown = it couldn't).

It worked before? I disabled HTML in my whole forum, but if it still works in signatures... Looks like I have to update to 6.0.2 asap.