Alex,

We discussed already earlier about database usage of unixtime or DATETIME.

Now, I looked into the Community comm_users and comm_sessions tables and found, that you use unix timestamp instead of DATEIME. As for comm_sessions table I would aggree to use unixtime.
But for comm_users table I don't not aggree. IMHO DATETIME would be better in that table.

In comm_users table, the comm_created and comm_lastlogin columns are unixtime based.
It means, that those possibilities to filter just by using an sql query LIKE '2003-12-10%' is impossible furthermore.
This possibility in Links SQL helps many times in filtering by a date. Now this is gone.
Additionally the possibility to use a database manager and check some info also gone, if you want to check any date right in the Community database...

I think, unixtime has not so much advantages of over DATETIME, to decide to use solely unixtime.
What are your reasons to use solely unixtime intead MySQL's internal DATETIME type?

Best regards,
Webmaster33

---

Paid Support from Webmaster33. Expert in Perl programming & Gossamer Threads applications. (click here for prices)
Webmaster33's products (upd.2004.09.26) | Private message | Contact me | Was my post helpful? Donate my help...