Comments on: Django: Big Integer Fields http://postneo.com/2005/08/26/django-big-integer-fields what comes next? Thu, 28 Jul 2011 15:59:37 +0000 hourly 1 http://wordpress.org/?v=3.1.2 By: grand-gambler.com http://postneo.com/2005/08/26/django-big-integer-fields/comment-page-1#comment-424466 grand-gambler.com Thu, 01 Apr 2010 01:07:00 +0000 http://www.postneo.com/?p=3759#comment-424466 I think the author or something keep back I think the author or something keep back

]]> By: helicopter skiing spain http://postneo.com/2005/08/26/django-big-integer-fields/comment-page-1#comment-52214 helicopter skiing spain Thu, 08 Feb 2007 12:26:57 +0000 http://www.postneo.com/?p=3759#comment-52214 <strong>helicopter skiing bis...</strong> skiing helicopter... helicopter skiing bis…

skiing helicopter…

]]> By: Ser http://postneo.com/2005/08/26/django-big-integer-fields/comment-page-1#comment-21538 Ser Sun, 06 Aug 2006 17:01:34 +0000 http://www.postneo.com/?p=3759#comment-21538 Good job. Good job.

]]> By: Adult Cartoon http://postneo.com/2005/08/26/django-big-integer-fields/comment-page-1#comment-12531 Adult Cartoon Mon, 17 Apr 2006 19:26:58 +0000 http://www.postneo.com/?p=3759#comment-12531 <a href="http://freecomics.blog.expedia.fr" rel="nofollow">porn comics</a> porn comics

]]> By: Usa http://postneo.com/2005/08/26/django-big-integer-fields/comment-page-1#comment-12523 Usa Mon, 17 Apr 2006 16:52:21 +0000 http://www.postneo.com/?p=3759#comment-12523 <a href="http://blog.superasianporn.info/ " rel="nofollow"> Asian porn</a> Asian porn

]]> By: petrilli http://postneo.com/2005/08/26/django-big-integer-fields/comment-page-1#comment-7358 petrilli Mon, 05 Sep 2005 06:14:09 +0000 http://www.postneo.com/?p=3759#comment-7358 Personally, I would penalize MySQL for violating the spec so eggregiously. Last I read, but it's been a while, the SQL spec doesn't discuss "unsigned" numbers. If you want to use unsigned numbers, I highly recommend you use a NUMERIC field of some sort to deal with it. While I'm all for "cross platform" SQL, I'm also for throwing out any platform that dumbs things down too far. I know MySQL is popular, but it's also heinously incompatible with PostgreSQL, Oracle, or any other commercial DB that I'm aware of. Personally, I would penalize MySQL for violating the spec so eggregiously. Last I read, but it’s been a while, the SQL spec doesn’t discuss “unsigned” numbers. If you want to use unsigned numbers, I highly recommend you use a NUMERIC field of some sort to deal with it.

While I’m all for “cross platform” SQL, I’m also for throwing out any platform that dumbs things down too far. I know MySQL is popular, but it’s also heinously incompatible with PostgreSQL, Oracle, or any other commercial DB that I’m aware of.

]]>