Comments on: Django: Big Integer Fields http://www.postneo.com/2005/08/26/django-big-integer-fields what comes next? Fri, 12 Mar 2010 23:21:39 +0000 http://wordpress.org/?v=2.0.5 by: helicopter skiing spain http://www.postneo.com/2005/08/26/django-big-integer-fields#comment-52214 Thu, 08 Feb 2007 12:26:57 +0000 http://www.postneo.com/2005/08/26/django-big-integer-fields#comment-52214 <strong>helicopter skiing bis...</strong> skiing helicopter... helicopter skiing bis…

skiing helicopter…

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

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

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

]]> by: petrilli http://www.postneo.com/2005/08/26/django-big-integer-fields#comment-7358 Mon, 05 Sep 2005 06:14:09 +0000 http://www.postneo.com/2005/08/26/django-big-integer-fields#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.

]]>