Comments on: Why you should not use BIT columns in MySQL http://www.xaprb.com/blog/2006/04/11/bit-values-in-mysql/ Stay curious! Fri, 10 May 2013 18:25:19 +0000 hourly 1 http://wordpress.org/?v=3.5.1 By: Per Persson http://www.xaprb.com/blog/2006/04/11/bit-values-in-mysql/#comment-20065 Per Persson Thu, 24 May 2012 15:19:11 +0000 http://www.xaprb.com/blog/?p=122#comment-20065 I’m using HeidiSQL. I found that this program has a peculiarity when it comes to bit fields. I created a BIT(4) field and populated it with numbers. HeidiSQL shows the numbers as bits, which is clearly better than what MySQL does, but in reverse! Thus 2 is shown as 0100, and 8 is shown as 0001.

]]> By: Pravin Singh http://www.xaprb.com/blog/2006/04/11/bit-values-in-mysql/#comment-19766 Pravin Singh Mon, 05 Dec 2011 11:58:16 +0000 http://www.xaprb.com/blog/?p=122#comment-19766 Good article. Thanks!!

]]> By: David L http://www.xaprb.com/blog/2006/04/11/bit-values-in-mysql/#comment-19443 David L Wed, 22 Jun 2011 11:14:19 +0000 http://www.xaprb.com/blog/?p=122#comment-19443 I realise that this is nothing to do with the article as such (interesting by the way), but you sould as if you could answer this.

In a routine in MySql 5.5 there seems to be no equivalent MySqlDBType for the SqlDBType.Char in MS SQL.

What should one use?

]]> By: daniel http://www.xaprb.com/blog/2006/04/11/bit-values-in-mysql/#comment-18979 daniel Thu, 09 Dec 2010 09:47:26 +0000 http://www.xaprb.com/blog/?p=122#comment-18979 It seems that the problem with joins was fixed, that’s correct? Your script no longer trigger any bug.

]]> By: Xaprb http://www.xaprb.com/blog/2006/04/11/bit-values-in-mysql/#comment-18978 Xaprb Wed, 08 Dec 2010 16:14:13 +0000 http://www.xaprb.com/blog/?p=122#comment-18978 Bool would probably be fine. I think it is a bad idea to pack multiple bits into a single variable-width column the way MySQL does. A bit column should be a single bit, and if you want multiple bits, you should define multiple columns.

]]>