blocks|key|775618|text|当您向表中添加位列时，它将占用每个记录中的整个字节，而不仅仅是一位。当您添加第二个位列时，它将存储在同一个字节中。第九位列将需要第二个字节的存储。具有1位列的表将不会获得任何存储好处。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|775619|Tinyint和bit都可以工作，我已经成功地使用了并且没有很强的偏好。|775620|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

When you add a bit column to your table it will occupy a whole byte in each record, not just a single bit. When you add a second bit column it will be stored in the same byte. The ninth bit column will require a second byte of storage. Tables with 1 bit column will not gain any storage benefit.

Tinyint and bit can both be made to work, I have used both successfully and have no strong preference.

blocks|key|774382|text|Bit...unless你是“真/假/文件找不到”家族的人|type|unstyled|depth|inlineStyleRanges|entityRanges|data|774383|万一你没拿到推荐信..。|offset|length|774384|在Linq2SQL的情况下，bit与true/false一起工作，这使得编程变得更加容易。两者都有好处。|774385|也有程序维护需要考虑。如果您(或初级实习生程序员)使用2、3、25、41、167、200等，会发生什么情况？哪里有文档？位是自文档化的，而且相当通用。|style|BOLD|774386|entityMap|0|LINK|mutability|MUTABLE|url|http://thedailywtf.com/Comments/Classic-WTF-What-Is-Truth.aspx^0|0|0|C|0|0|0|1O|7|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@]|9|@$D|V|E|W|1|X]]|A|$]]|$1|F|3|G|5|6|7|Y|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|Z|8|@$D|10|E|11|J|K]]|9|@]|A|$]]|$1|L|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S]]]]

Bit...unless you're of the "true / false / file not found" clan

<a href="http://thedailywtf.com/Comments/Classic-WTF-What-Is-Truth.aspx" rel="noreferrer">In case you didn't get the reference...</a>

And in the case of Linq2SQL, bit works with true/false which makes it easier to program for. There's advantages to both.

And there's also programming maintenance to consider. What happens if you (or a junior intern programmer) uses a 2, 3, 25, 41, 167, 200 etc? Where is that documented? Bits are self-documenting and pretty universal.

blocks|key|775606|text|我在适当的时候使用比特。除了语义上正确的类型(语义计数！)之外，单个行(至少在Server上)中的多个位字段(最多8位)可以合并成一个存储字节。在第八个字节之后，接下来的8个还需要一个额外的字节，依此类推。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|775607|参考文献：|775608|SQL+2000|unordered-list-item|offset|length|775609|SQL+2005|775610|SQL+2008|775611|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/aa225961(SQL.80).aspx|1|http://msdn.microsoft.com/en-us/library/ms177603(SQL.90).aspx|2|http://msdn.microsoft.com/en-us/library/ms177603.aspx^0|0|0|0|8|0|0|0|8|1|0|0|8|2|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Z|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|10|8|@]|9|@$G|11|H|12|1|13]]|A|$]]|$1|I|3|J|5|F|7|14|8|@]|9|@$G|15|H|16|1|17]]|A|$]]|$1|K|3|L|5|F|7|18|8|@]|9|@$G|19|H|1A|1|1B]]|A|$]]|$1|M|3|-4|5|6|7|1C|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|T]]|U|$5|P|Q|R|A|$S|V]]|W|$5|P|Q|R|A|$S|X]]]]

I use bits when appropriate. Aside from it being semantically the correct type (semantics count!), multiple bit fields (up to 8) in a single row (on SQL Server, anyway) can be consolidated into a single byte of storage. After the eighth, an additional byte is needed for the next 8, and so on.

References:

<ul>
<li><a href="http://msdn.microsoft.com/en-us/library/aa225961(SQL.80).aspx" rel="noreferrer">SQL 2000</a></li>
<li><a href="http://msdn.microsoft.com/en-us/library/ms177603(SQL.90).aspx" rel="noreferrer">SQL 2005</a></li>
<li><a href="http://msdn.microsoft.com/en-us/library/ms177603.aspx" rel="noreferrer">SQL 2008</a></li>
</ul>

blocks|key|482944|text|对于MySql用户-+为什么不应在MySQL中使用位列|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|482945|entityMap|0|LINK|mutability|MUTABLE|url|http://www.xaprb.com/blog/2006/04/11/bit-values-in-mysql/^0|B|G|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

For MySql users - <a href="http://www.xaprb.com/blog/2006/04/11/bit-values-in-mysql/" rel="noreferrer">Why you should not use BIT columns in MySQL</a>

blocks|key|482917|text|StackOverflow上一篇文章：在MySQL中，BIT和TINYINT有什么区别？|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|482918|当添加新的"BOOL“列时，MySQL实际上使用了TINYINT。|482919|我只想坚持BOOL+(又名TINYINT)，继续生活。|style|BOLD|482920|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/290223/what-is-the-difference-between-bit-and-tinyint-in-mysql^0|J|P|0|0|0|5|4|D|7|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]]|C|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|W|8|@$A|X|B|Y|H|I]|$A|Z|B|10|H|I]]|9|@]|C|$]]|$1|J|3|-4|5|6|7|11|8|@]|9|@]|C|$]]]|K|$L|$5|M|N|O|C|$P|Q]]]]

A previous StackOverflow post: <a href="https://stackoverflow.com/questions/290223/what-is-the-difference-between-bit-and-tinyint-in-mysql">What is the difference between BIT and TINYINT in MySQL?</a>

When adding a new "BOOL" column, MySQL actually uses TINYINT.

I'd just stick with BOOL (aka TINYINT) and move on with life.

blocks|key|774416|text|根据定义，布尔值只允许两个值。为什么你只需要一点就够了？如果您需要一个三(或更多)状态逻辑，那么使用更大的数据类型，但是对于标准布尔逻辑，我会(并且确实)坚持使用位字段。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|774417|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Boolean, by definition, allows only two values. Why would you need anything more than a single bit for this? if you need a three (or more) state logic, then use a bigger datatype, but I would (and do) stick with bit fields for standard boolean logic.

blocks|key|483059|text|我使用bit是因为它省去了我必须使用一个check约束，而且因为我的ORM将自动地将位转换成一个可空布尔值(C#)，这一点我非常欣赏。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|483060|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I use bit because it saves me having to use a check constraint, and because my ORM will automatically convert bit into a nullable boolean (C#), which I very much appreciate once coding.

blocks|key|774554|text|伪的零空间|type|unstyled|depth|inlineStyleRanges|entityRanges|data|774555|无论您选择什么，您都可以设置为NULL，而不是0，它不会占用额外的空间(因为数据库几乎总是对每一行的每个字段都有一个NULL标志，就坐在那里；这里有更多的信息)。如果您还确保默认值/最有可能的值是false，您将节省更多的空间！|offset|length|style|CODE|774556|真的一些空间|BOLD|774557|表示true的值需要由字段类型定义的空间；只有当一个表有多个这样的列时，使用BIT才能节省空间，因为它每8个字段使用一个字节(而TINYINT每个字段使用一个字节)。|774558|TINYINT的优点是您可以定制一个8值的位掩码，而不必担心管理一堆额外的列，而且理论上搜索速度更快(一个整数字段相对于几个位字段)。但是也有一些缺点，比如排序慢，索引复杂，字段名少等。对我来说，这是最大的损失；您的数据库需要外部文档来记录哪些位在哪个位掩码中做了什么。|774559|无论如何，避免使用TEXT字段来存储布尔值或布尔值集的诱惑。搜索文本对于服务器来说是一项很大的工作，任意命名方案，如“打开、关闭、关闭”，都会损害互操作性。|774560|entityMap|0|LINK|mutability|MUTABLE|url|http://www.sqlskills.com/blogs/paul/misconceptions-around-null-bitmap-size/|1|http://www.ugrad.cs.ubc.ca/~cs490/sec202/notes/intro/bitmask.pdf^0|0|F|4|N|1|1M|4|2Q|5|1Z|8|0|0|0|1|0|2|4|12|3|1S|7|0|0|7|L|3|1|0|9|4|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|11|8|@$D|12|E|13|F|G]|$D|14|E|15|F|G]|$D|16|E|17|F|G]|$D|18|E|19|F|G]]|9|@$D|1A|E|1B|1|1C]]|A|$]]|$1|H|3|I|5|6|7|1D|8|@$D|1E|E|1F|F|J]]|9|@]|A|$]]|$1|K|3|L|5|6|7|1G|8|@$D|1H|E|1I|F|G]|$D|1J|E|1K|F|G]|$D|1L|E|1M|F|G]]|9|@]|A|$]]|$1|M|3|N|5|6|7|1N|8|@$D|1O|E|1P|F|G]]|9|@$D|1Q|E|1R|1|1S]]|A|$]]|$1|O|3|P|5|6|7|1T|8|@$D|1U|E|1V|F|G]]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|1W|8|@]|9|@]|A|$]]]|R|$S|$5|T|U|V|A|$W|X]]|Y|$5|T|U|V|A|$W|Z]]]]

Zero Space for False

Whatever your choice, you can set to <code>NULL</code> instead of <code>0</code> and it will take up no extra space (since the database almost always has a <code>NULL</code> flag for every field of every row, just sitting there; <a href="http://www.sqlskills.com/blogs/paul/misconceptions-around-null-bitmap-size/" rel="nofollow">more info here</a>). If you also make sure the default/most likely value is <code>false</code>, you'll save even more space!

Some Space for True

The value to represent <code>true</code> requires the space defined by the field type; using <code>BIT</code> will only save space if a table has multiple such columns, since it uses one byte per 8 fields (versus <code>TINYINT</code> which uses one byte per field).

<code>TINYINT</code> has the advantage of allowing you to customize an 8-value <a href="http://www.ugrad.cs.ubc.ca/~cs490/sec202/notes/intro/bitmask.pdf" rel="nofollow">bitmask</a> without worrying about managing a bunch of extra columns, and searching is theoretically faster (a single integer field versus several bit fields). But there are some disadvantages such as slower ordering, fancy cross-indexing stuff, and lack of field names. Which to me, is the biggest loss; your database would require external documentation to note which bits did what in which bitmasks.

In any case, avoid the temptation to use <code>TEXT</code> fields to store booleans or sets of them. Searching through text is a lot more work for the server, and arbitrary naming schemes like "on, off, off" can hurt interoperability.

blocks|key|2015694|text|我刚刚试着对bit进行分组(SQLServer2k5)，它对我来说很好。我喜欢为应用程序使用正确的数据类型。如果它是一个真/假字段，那么bit就是我所用的.|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2015695|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I just tried grouping on bit (SQL Server 2k5) and it worked fine for me. I like using the correct data type for the application. If it's a true/false field, then bit is what i use...

blocks|key|775655|text|所有这些理论上的讨论都是很棒的，但实际上，至少如果您使用的是MySQL，实际上也适用于SQLServer，那么最好坚持使用非二进制数据，因为在输出数据、查询等等时，使用非二进制数据更容易。如果您试图在MySQL和SQLServer之间实现互操作性(即在两者之间同步数据)，这一点尤其重要，因为在这两者中位数据类型的处理是不同的。因此，在实践中，如果坚持使用数字数据类型，那么麻烦就会少得多。我建议MySQL继续使用BOOL或布尔值，后者存储为TINYINT(1)。即使是MySQL工作台和MySQL管理员显示位数据类型的方式也不太好(它是二进制数据的一个小符号)。所以要讲求实际，省去麻烦(不幸的是，我是从经验中说出来的)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|775656|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

All these theorentical discussions are great, but in reality, at least if you're using MySQL and really for SQLServer as well, it's best to stick with non-binary data for your booleans for the simple reason that it's easier to work with when you're outputting the data, querying and so on. It is especially important if you're trying to achieve interoperability between MySQL and SQLServer (i.e. you sync data between the two), because the handling of BIT datatype is different in the two of them. SO in practice you will have a lot less hassles if you stick with a numeric datatype. I would recommend for MySQL to stick with BOOL or BOOLEAN which gets stored as TINYINT(1). Even the way MySQL Workbench and MySQL Administrator display the BIT datatype isn't nice (it's a little symbol for binary data). So be practical and save yourself the hassles (and unfortunately I'm speaking from experience).

blocks|key|774546|text|我想我没有看到上面提到过，但是存在不能聚合位列的问题(例如MIN、MAX，特别是SUM)。我刚刚用2008年进行了测试，问题仍然存在。这是我最近使用tinyint的最大原因--另一个原因是我喜欢tinyint的大小--当您的“双值”位标志突然需要更多可能的值时，这总是很痛苦的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|774547|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I don't think I saw it mentioned above, but there's the issue of not being able to aggregate BIT columns (e.g. MIN, MAX, and especially SUM). I just tested using 2008 and the issue is still there. That's the biggest reason I use tinyint lately - the other being I like how tinyint scales - it's always a pain when your "two-value" bit flag suddenly needs more possible values.

blocks|key|775542|text|我们用一个int“向量”字段构建我们所有的表。然后，我们使用该字段作为32位的集合，我们可以为任何目的分配这些位。(可能对一组状态使用一组位)。避免了如果我们忘记了就必须继续添加标记字段。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|775543|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

We build all our tables with an int "vector" field. We then use that field as a collection of 32 bits that we can assign for any purpose. (Potentially using a group of bits for a set of states). Avoids us having to keep adding in flag fields if we forget.

blocks|key|774454|text|@Kevin：我相信您可以在位字段上使用group+by+(+Server+2005)：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|774455|declare+@t+table+(
++++descr+varchar(10),
++++myBit1+bit,+
++++myBit2+bit
)
insert+into+@t+values+('test1',+0,+1)
insert+into+@t+values+('test2',+1,+0)
insert+into+@t+values+('test3',+1,+1)
insert+into+@t+values+('test4',+0,+0)

select+myBit1,+count(myBit1)+from+@t+group+by+myBit1
select+myBit2,+count(myBit1)+from+@t+group+by+myBit2|code-block|syntax|javascript|774456|结果：|774457|myBit1+
------+-----------
0++++++2
1++++++2

myBit2+
------+-----------
0++++++2
1++++++2|774458|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/488811/tinyint-vs-bit#488815^0|K|8|0|7|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@$9|X|A|Y|B|C]]|D|@$9|Z|A|10|1|11]]|E|$]]|$1|F|3|G|5|H|7|12|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|13|8|@]|D|@]|E|$]]|$1|M|3|N|5|H|7|14|8|@]|D|@]|E|$I|J]]|$1|O|3|-4|5|6|7|15|8|@]|D|@]|E|$]]]|P|$Q|$5|R|S|T|E|$U|V]]]]

<a href="https://stackoverflow.com/questions/488811/tinyint-vs-bit#488815">@Kevin:</a> I believe you can use <code>group by</code> on bit fields (SQL Server 2005):

<pre><code>declare @t table (
 descr varchar(10),
 myBit1 bit, 
 myBit2 bit
)
insert into @t values ('test1', 0, 1)
insert into @t values ('test2', 1, 0)
insert into @t values ('test3', 1, 1)
insert into @t values ('test4', 0, 0)

select myBit1, count(myBit1) from @t group by myBit1
select myBit2, count(myBit1) from @t group by myBit2
</code></pre>

Results:

<pre><code>myBit1 
------ -----------
0 2
1 2

myBit2 
------ -----------
0 2
1 2
</code></pre>

blocks|key|2015997|text|TinyInt是我的首选。然后，当对字段进行聚合计数时，不必转换它。此外，一些前端语言的解释与其他语言略有不同，并且使用TinyInt使验证检查对于任何前端语言都是通用的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2015998|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

TinyInt is my preference. Then, when doing aggregated counts against the field, you don't have to cast it. Also, some front-end languages interpret a Bit differently than others, and using a TinyInt makes validation checks universal for any front-end language.

blocks|key|774474|text|如果您使用的是MySQL，则不建议使用位数据类型-+http://www.xaprb.com/blog/2006/04/11/bit-values-in-mysql/|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|774475|entityMap|0|LINK|mutability|MUTABLE|url|http://www.xaprb.com/blog/2006/04/11/bit-values-in-mysql/^0|Q|1L|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

If you're using MySQL, then it's not recommended to use the BIT data type - <a href="http://www.xaprb.com/blog/2006/04/11/bit-values-in-mysql/" rel="nofollow noreferrer">http://www.xaprb.com/blog/2006/04/11/bit-values-in-mysql/</a>

blocks|key|2015900|text|我喜欢与'T‘或'F’连用char(1)。是的，它可以与其他值一起使用，但至少在报告或其他更难使用位或二进制值的地方很容易查看。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2015901|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I like using char(1) with 'T' or 'F'. Yes it can be abused with other values but at least it is easy to view in reports or other places where bit or binary values are harder to work with.

I don't want to touch-off a religious war here, but there seem to be two schools of thoughts in how to represent boolean values in a database. Some say <code>bit</code> is the appropriate data type, while others argue <code>tinyint</code> is better.

The only differences I'm aware of are these:

<ul>
<li><code>bit</code>: storage size is 1 bit, possible values are 0 or 1</li>
<li><code>tinyint</code>: storage size is 1 byte, possible values are 0-255</li>
</ul>

Which data type is better when you need to represent boolean values? Is <code>tinyint</code> worth the extra overhead "just in case" you need to values > 1?

Tinyint vs Bit?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我不想在这里引发一场宗教战争，但在如何在数据库中表示布尔值方面，似乎有两种观点。有些人认为bit是合适的数据类型，而另一些人则认为tinyint更好。我所知道的唯一不同之处是：bit：存储大小为1位，可能值为0或1tinyint：存储大小为1字节，可能值为0-255。当您需要表示布尔值时，哪种数据类型更好？tinyint是否值得额外的开销“以防万一”您需要值> 1？

问丁丁对比特？
EN

回答 16

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问丁丁对比特？EN

回答 16

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问丁丁对比特？
EN