Comments on: Fun with SQL http://www.simonbuckle.com/2006/04/05/fun-with-sql/ Random thoughts for random people Tue, 03 Jan 2012 16:29:00 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Simon http://www.simonbuckle.com/2006/04/05/fun-with-sql/comment-page-1/#comment-66 Simon Thu, 06 Apr 2006 09:28:57 +0000 http://www.simonbuckle.com/2006/04/05/fun-with-sql/#comment-66 I agree that it is odd. I just expected it to be a standard date type so you can imagine my surprise when I got the error. According to the documentation this is because "date column type support varies widely across databases. Therefore, Wildfire specially encodes dates as VARCHAR values. Each date is a Java long value which is 0-padded to 15 characters." The database schema documentation is <a href="http://www.jivesoftware.org/builds/wildfire/docs/latest/documentation/database-guide.html" rel="nofollow">here</a>. I agree that it is odd. I just expected it to be a standard date type so you can imagine my surprise when I got the error.

According to the documentation this is because “date column type support varies widely across databases. Therefore, Wildfire specially encodes dates as VARCHAR values. Each date is a Java long value which is 0-padded to 15 characters.”

The database schema documentation is here.

]]> By: Miles Barr http://www.simonbuckle.com/2006/04/05/fun-with-sql/comment-page-1/#comment-65 Miles Barr Thu, 06 Apr 2006 09:12:21 +0000 http://www.simonbuckle.com/2006/04/05/fun-with-sql/#comment-65 How odd. Did the authors give any indication why they needed such fine grained times? I would have thought the day would suffice. How odd. Did the authors give any indication why they needed such fine grained times? I would have thought the day would suffice.

]]>