It's quite simple, it's unsigned because Unix epoch can't be negative. Only problem with using Unix epoch is year 2038 when it will end...
On Sep 14, 3:17 pm, Andy C <[EMAIL PROTECTED]> wrote: > I find the design decision to change the data type of the > posts.pubdate column (et al) to an unsigned integer bizarre in the > extreme. > > In modern databases, a date is normally represented a date which makes > sense. For example, this change now makes using SQL to select posts > difficult. > > I don't doubt PHP has built in functions to convert Unix epoch numbers > to dates and times in lots of formats. > > Don't get me wrong - I am now on the latest SVN and like the timezone > support (and scheduled posts) but out of idle curiosity, what was the > rationale for this ? --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/habari-dev -~----------~----~----~----~------~----~------~--~---
