count(*) VS count(X)

最新推荐文章于 2021-02-16 22:34:24 发布
最新推荐文章于 2021-02-16 22:34:24 发布
阅读量134 收藏
点赞数
文章标签： 数据库
原文链接：https://yq.aliyun.com/articles/379946
版权

背景

在平时的工作中，有些同学对count的用法还是有疑惑的，为此我做个简单的总结和测试，希望对大家有帮助。

count(*)和count(X)是不等价的

表达式
含义
count(*)
返回总行数，包括空和非空值
count(expression)
返回expression中的非空值，例如count(1)或count(0)和count(*)等价
count(column)
只返回column的非空值

不同类型的count的速度是不一样的

因为MyISAM已经在一个表里缓存了表数据量，MyISAM可以很快的返回count(*)或者count(not null)的值，如果想count(column can be null)的话就会比较慢，因为count可以为null的列要遍历列的数据的。
举个例子：

show create table sbtest1\G
*************************** 1. row ***************************
       Table: sbtest1
Create Table: CREATE TABLE `sbtest1` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
  `gmt_create` datetime NOT NULL,
  `gmt_modified` datetime NOT NULL,
  `k` int(11) DEFAULT NULL,
  `c` varchar(500) NOT NULL DEFAULT '',
  `pad` char(60) NOT NULL DEFAULT '',
  `is_used` int(11) NOT NULL DEFAULT '0',
  PRIMARY KEY (`id`),
  KEY `k_1` (`k`)
) ENGINE=InnoDB AUTO_INCREMENT=69313841 DEFAULT CHARSET=latin1

测试环境

Server version: 5.7.20 MySQL Community Server (GPL)
32核 128G

执行计划

mysql> explain extended select count(*) from sbtest1;
+----+-------------+---------+------------+-------+---------------+------+---------+------+----------+----------+-------------+
| id | select_type | table   | partitions | type  | possible_keys | key  | key_len | ref  | rows     | filtered | Extra       |
+----+-------------+---------+------------+-------+---------------+------+---------+------+----------+----------+-------------+
|  1 | SIMPLE      | sbtest1 | NULL       | index | NULL          | k_1  | 5       | NULL | 25926320 |   100.00 | Using index |
+----+-------------+---------+------------+-------+---------------+------+---------+------+----------+----------+-------------+
1 row in set, 2 warnings (0.00 sec)

mysql> explain extended select count(0) from sbtest1;
+----+-------------+---------+------------+-------+---------------+------+---------+------+----------+----------+-------------+
| id | select_type | table   | partitions | type  | possible_keys | key  | key_len | ref  | rows     | filtered | Extra       |
+----+-------------+---------+------------+-------+---------------+------+---------+------+----------+----------+-------------+
|  1 | SIMPLE      | sbtest1 | NULL       | index | NULL          | k_1  | 5       | NULL | 25926320 |   100.00 | Using index |
+----+-------------+---------+------------+-------+---------------+------+---------+------+----------+----------+-------------+
1 row in set, 2 warnings (0.00 sec)

mysql> explain extended select count(1) from sbtest1;
+----+-------------+---------+------------+-------+---------------+------+---------+------+----------+----------+-------------+
| id | select_type | table   | partitions | type  | possible_keys | key  | key_len | ref  | rows     | filtered | Extra       |
+----+-------------+---------+------------+-------+---------------+------+---------+------+----------+----------+-------------+
|  1 | SIMPLE      | sbtest1 | NULL       | index | NULL          | k_1  | 5       | NULL | 25926320 |   100.00 | Using index |
+----+-------------+---------+------------+-------+---------------+------+---------+------+----------+----------+-------------+
1 row in set, 2 warnings (0.00 sec)

mysql> explain extended select count(id) from sbtest1;
+----+-------------+---------+------------+-------+---------------+------+---------+------+----------+----------+-------------+
| id | select_type | table   | partitions | type  | possible_keys | key  | key_len | ref  | rows     | filtered | Extra       |
+----+-------------+---------+------------+-------+---------------+------+---------+------+----------+----------+-------------+
|  1 | SIMPLE      | sbtest1 | NULL       | index | NULL          | k_1  | 5       | NULL | 25926320 |   100.00 | Using index |
+----+-------------+---------+------------+-------+---------------+------+---------+------+----------+----------+-------------+
1 row in set, 2 warnings (0.00 sec)

mysql> explain extended select count(k) from sbtest1;
+----+-------------+---------+------------+-------+---------------+------+---------+------+----------+----------+-------------+
| id | select_type | table   | partitions | type  | possible_keys | key  | key_len | ref  | rows     | filtered | Extra       |
+----+-------------+---------+------------+-------+---------------+------+---------+------+----------+----------+-------------+
|  1 | SIMPLE      | sbtest1 | NULL       | index | NULL          | k_1  | 5       | NULL | 25926320 |   100.00 | Using index |
+----+-------------+---------+------------+-------+---------------+------+---------+------+----------+----------+-------------+
1 row in set, 2 warnings (0.00 sec)

测试的SQL

[root@localhost ~]# mysqlslap -h 127.0.0.1 -P 3306 -u root -p'123456' --iterations=30 --concurrency=1 --number-of-queries=1 --create-schema='test' --query='select count(*) from sbtest1'
Benchmark
    Average number of seconds to run all queries: 4.295 seconds
    Minimum number of seconds to run all queries: 4.197 seconds
    Maximum number of seconds to run all queries: 4.463 seconds
    Number of clients running queries: 1
    Average number of queries per client: 1

[root@localhost ~]# mysqlslap -h 127.0.0.1 -P 3306 -u root -p'123456' --iterations=30 --concurrency=1 --number-of-queries=1 --create-schema='test' --query='select count(0) from sbtest1'
Benchmark
    Average number of seconds to run all queries: 4.277 seconds
    Minimum number of seconds to run all queries: 4.192 seconds
    Maximum number of seconds to run all queries: 4.452 seconds
    Number of clients running queries: 1
    Average number of queries per client: 1

[root@localhost ~]# mysqlslap -h 127.0.0.1 -P 3306 -u root -p'123456' --iterations=30 --concurrency=1 --number-of-queries=1 --create-schema='test' --query='select count(1) from sbtest1'
Benchmark
    Average number of seconds to run all queries: 4.281 seconds
    Minimum number of seconds to run all queries: 4.188 seconds
    Maximum number of seconds to run all queries: 4.849 seconds
    Number of clients running queries: 1
    Average number of queries per client: 1

[root@localhost ~]# mysqlslap -h 127.0.0.1 -P 3306 -u root -p'123456' --iterations=30 --concurrency=1 --number-of-queries=1 --create-schema='test' --query='select count(id) from sbtest1'
Benchmark
    Average number of seconds to run all queries: 4.716 seconds
    Minimum number of seconds to run all queries: 4.631 seconds
    Maximum number of seconds to run all queries: 4.778 seconds
    Number of clients running queries: 1
    Average number of queries per client: 1

[root@localhost ~]# mysqlslap -h 127.0.0.1 -P 3306 -u root -p'123456' --iterations=30 --concurrency=1 --number-of-queries=1 --create-schema='test' --query='select count(k) from sbtest1'
Benchmark
    Average number of seconds to run all queries: 4.832 seconds
    Minimum number of seconds to run all queries: 4.739 seconds
    Maximum number of seconds to run all queries: 5.054 seconds
    Number of clients running queries: 1
    Average number of queries per client: 1

从上面的测试可以看出查询速度：count(expression) > count(*) > count(column not null) > count( column can be null )
值得说明的是:
count(column not null) > count( column can be null ) 对于不同的列并不是绝对的，对于同一列的count(column not null) > count( column can be null )这个仍然是成立的。
比如：

mysql> alter table sbtest1 add index idx_is_used (is_used);
Query OK, 0 rows affected (1 min 43.12 sec)
Records: 0  Duplicates: 0  Warnings: 0
mysql> alter table sbtest1 add index idx_gmt_create (gmt_create);
Query OK, 0 rows affected (1 min 49.33 sec)
Records: 0  Duplicates: 0  Warnings: 0

跑出来的结果是：

[root@localhost ~]# mysqlslap -h 127.0.0.1 -P 3306 -u root -p'123456' --iterations=30 --concurrency=1 --number-of-queries=1 --create-schema='test' --query='select count(is_used) from sbtest1'
Benchmark
    Average number of seconds to run all queries: 5.391 seconds
    Minimum number of seconds to run all queries: 5.222 seconds
    Maximum number of seconds to run all queries: 5.494 seconds
    Number of clients running queries: 1
    Average number of queries per client: 1
[root@localhost ~]# mysqlslap -h 127.0.0.1 -P 3306 -u root -p'123456' --iterations=30 --concurrency=1 --number-of-queries=1 --create-schema='test' --query='select count(gmt_create) from sbtest1'
Benchmark
    Average number of seconds to run all queries: 5.187 seconds
    Minimum number of seconds to run all queries: 5.104 seconds
    Maximum number of seconds to run all queries: 5.321 seconds
    Number of clients running queries: 1
    Average number of queries per client: 1

这两列is_used和gmt_create都是非空，而k是是可空，但是查询速度却没有count(k)快，原因是什么呢？我们来看下执行计划：

mysql> explain select count(gmt_create) from sbtest1;
+----+-------------+---------+------------+-------+---------------+----------------+---------+------+----------+----------+-------------+
| id | select_type | table   | partitions | type  | possible_keys | key            | key_len | ref  | rows     | filtered | Extra       |
+----+-------------+---------+------------+-------+---------------+----------------+---------+------+----------+----------+-------------+
|  1 | SIMPLE      | sbtest1 | NULL       | index | NULL          | idx_gmt_create | 5       | NULL | 25931936 |   100.00 | Using index |
+----+-------------+---------+------------+-------+---------------+----------------+---------+------+----------+----------+-------------+
1 row in set, 1 warning (0.00 sec)

mysql> explain select count(is_used) from sbtest1;
+----+-------------+---------+------------+-------+---------------+-------------+---------+------+----------+----------+-------------+
| id | select_type | table   | partitions | type  | possible_keys | key         | key_len | ref  | rows     | filtered | Extra       |
+----+-------------+---------+------------+-------+---------------+-------------+---------+------+----------+----------+-------------+
|  1 | SIMPLE      | sbtest1 | NULL       | index | NULL          | idx_is_used | 4       | NULL | 25931936 |   100.00 | Using index |
+----+-------------+---------+------------+-------+---------------+-------------+---------+------+----------+----------+-------------+
1 row in set, 1 warning (0.00 sec)

mysql> explain select count(k) from sbtest1;
+----+-------------+---------+------------+-------+---------------+------+---------+------+----------+----------+-------------+
| id | select_type | table   | partitions | type  | possible_keys | key  | key_len | ref  | rows     | filtered | Extra       |
+----+-------------+---------+------------+-------+---------------+------+---------+------+----------+----------+-------------+
|  1 | SIMPLE      | sbtest1 | NULL       | index | NULL          | k_1  | 4       | NULL | 25931936 |   100.00 | Using index |
+----+-------------+---------+------------+-------+---------------+------+---------+------+----------+----------+-------------+
1 row in set, 1 warning (0.00 sec)

我们再改变下列的形式：

mysql> alter table sbtest1 change column k k int(11) NOT NULL DEFAULT '0';
Query OK, 0 rows affected (17 min 44.57 sec)
Records: 0  Duplicates: 0  Warnings: 0

再跑下：

[root@localhost ~]# mysqlslap -h 127.0.0.1 -P 3306 -u root -p'015891' --iterations=30 --concurrency=1 --number-of-queries=1 --create-schema='test' --query='select count(k) from sbtest1'
Benchmark
    Average number of seconds to run all queries: 4.684 seconds
    Minimum number of seconds to run all queries: 4.528 seconds
    Maximum number of seconds to run all queries: 4.812 seconds
    Number of clients running queries: 1
    Average number of queries per client: 1

对比之前的压测结果：对于k列非空比空快（4.684 < 4.832）。

count带where场景

在实际的应用场景中，已经有其他方法代替不带where条件的count(比如预估值，比如计数器等)，很多带where条件的是需要count的，那这类SQL的速度是什么样的呢？

[root@localhost ~]# mysqlslap -h 127.0.0.1 -P 3306 -u root -p'123456' --iterations=30 --concurrency=1 --number-of-queries=1 --create-schema='test' --query='select count(*) from sbtest1 where id>1000000'
Benchmark
    Average number of seconds to run all queries: 6.696 seconds
    Minimum number of seconds to run all queries: 6.508 seconds
    Maximum number of seconds to run all queries: 6.817 seconds
    Number of clients running queries: 1
    Average number of queries per client: 1
[root@localhost ~]# mysqlslap -h 127.0.0.1 -P 3306 -u root -p'123456' --iterations=30 --concurrency=1 --number-of-queries=1 --create-schema='test' --query='select count(0) from sbtest1 where id>1000000'
Benchmark
    Average number of seconds to run all queries: 6.717 seconds
    Minimum number of seconds to run all queries: 6.490 seconds
    Maximum number of seconds to run all queries: 6.865 seconds
    Number of clients running queries: 1
    Average number of queries per client: 1
[root@localhost ~]# mysqlslap -h 127.0.0.1 -P 3306 -u root -p'123456' --iterations=30 --concurrency=1 --number-of-queries=1 --create-schema='test' --query='select count(1) from sbtest1 where id>1000000'
Benchmark
    Average number of seconds to run all queries: 6.656 seconds
    Minimum number of seconds to run all queries: 6.519 seconds
    Maximum number of seconds to run all queries: 6.859 seconds
    Number of clients running queries: 1
    Average number of queries per client: 1
[root@localhost ~]# mysqlslap -h 127.0.0.1 -P 3306 -u root -p'123456' --iterations=30 --concurrency=1 --number-of-queries=1 --create-schema='test' --query='select count(id) from sbtest1 where id>1000000'
Benchmark
    Average number of seconds to run all queries: 6.691 seconds
    Minimum number of seconds to run all queries: 6.514 seconds
    Maximum number of seconds to run all queries: 6.865 seconds
    Number of clients running queries: 1
    Average number of queries per client: 1

执行计划

mysql> explain select count(id) from sbtest1 where id>1000000;
+----+-------------+---------+------------+-------+---------------+---------+---------+------+----------+----------+--------------------------+
| id | select_type | table   | partitions | type  | possible_keys | key     | key_len | ref  | rows     | filtered | Extra                    |
+----+-------------+---------+------------+-------+---------------+---------+---------+------+----------+----------+--------------------------+
|  1 | SIMPLE      | sbtest1 | NULL       | range | PRIMARY       | PRIMARY | 4       | NULL | 12963160 |   100.00 | Using where; Using index |
+----+-------------+---------+------------+-------+---------------+---------+---------+------+----------+----------+--------------------------+
1 row in set, 1 warning (0.00 sec)

mysql> explain select count(*) from sbtest1 where id>1000000;
+----+-------------+---------+------------+-------+---------------+---------+---------+------+----------+----------+--------------------------+
| id | select_type | table   | partitions | type  | possible_keys | key     | key_len | ref  | rows     | filtered | Extra                    |
+----+-------------+---------+------------+-------+---------------+---------+---------+------+----------+----------+--------------------------+
|  1 | SIMPLE      | sbtest1 | NULL       | range | PRIMARY       | PRIMARY | 4       | NULL | 12963160 |   100.00 | Using where; Using index |
+----+-------------+---------+------------+-------+---------------+---------+---------+------+----------+----------+--------------------------+
1 row in set, 1 warning (0.00 sec)

mysql> explain select count(0) from sbtest1 where id>1000000;
+----+-------------+---------+------------+-------+---------------+---------+---------+------+----------+----------+--------------------------+
| id | select_type | table   | partitions | type  | possible_keys | key     | key_len | ref  | rows     | filtered | Extra                    |
+----+-------------+---------+------------+-------+---------------+---------+---------+------+----------+----------+--------------------------+
|  1 | SIMPLE      | sbtest1 | NULL       | range | PRIMARY       | PRIMARY | 4       | NULL | 12963160 |   100.00 | Using where; Using index |
+----+-------------+---------+------------+-------+---------------+---------+---------+------+----------+----------+--------------------------+
1 row in set, 1 warning (0.00 sec)

mysql> explain select count(1) from sbtest1 where id>1000000;
+----+-------------+---------+------------+-------+---------------+---------+---------+------+----------+----------+--------------------------+
| id | select_type | table   | partitions | type  | possible_keys | key     | key_len | ref  | rows     | filtered | Extra                    |
+----+-------------+---------+------------+-------+---------------+---------+---------+------+----------+----------+--------------------------+
|  1 | SIMPLE      | sbtest1 | NULL       | range | PRIMARY       | PRIMARY | 4       | NULL | 12963160 |   100.00 | Using where; Using index |
+----+-------------+---------+------------+-------+---------------+---------+---------+------+----------+----------+--------------------------+
1 row in set, 1 warning (0.00 sec)

在这类场景中count(expression)>count(id)>count(*), count(id)和count(*) 微差。

 另外在5.7中也做了一些改动，“[会根据flag判断是否可以把count(*)下推到引擎层，由于只有一次引擎层的调用，减少了Server层和InnoDB的交互，避免了无谓的内存操作或格式转换](http://mysql.taobao.org/monthly/2016/06/10/)”，从这个角度讲好像是优化了count（*），但是“[由于总是强制使用聚集索引，缺点很明显：当二级索引的大小远小于聚集索引，且数据不在内存中时，使用二级索引显然要快些，因此文件IO更少。](http://mysql.taobao.org/monthly/2016/06/10/)”

结论

  • count(expression)比count(*)和count(column)，如果没有特殊业务含义的话，可以优先使用
  • 到底是使用count(*)快还是count(column)快，这个也不是一定的

参考

https://dev.mysql.com/doc/refman/5.6/en/group-by-functions.html#function_count
http://www.rndblog.com/mysql-select-count/
http://www.mysqldiary.com/limited-select-count/
http://mysqlha.blogspot.com/2009/08/fast-count-for-innodb.html

weixin_34088598
关注
【实习】MySQL-select count(*)和select count(1)
爱写bug的王六六
07-08 1008
MySQL
hive里面select count(*)为0，select * 有数据
zxlstart的博客
12-17 3143
项目场景： 在hive 中执行select count(1) from table_a 结果显示是0 问题描述： hive 中使用select count(1) from table_a 查询结果显示是0，但使用 select count(table_a.x) from table_a 查询结果却不是0。 select count(1) from jdc where rfq ='20201215'; select count(sbbh) from jdc where rfq ='20201215';
【经典解释】count(1)，count(*)，count(x)之间的区别
CodingLJ
12-26 1961
1.count(*) count(*) 是计算整个表的行数。 一个表有多行，只要每行有一个字段不为空，这一行就会计数。 2.count(1) count(1) 是也是计算的是整个表的行。 这边就是计算的是左边标记的1的个数 3.count(x) count(x),这里面的x就是一个标记计数的，可以是2 ，3，就是计算2,3的个数 ...
distinct() vs count()
10-14 60
SQL&gt; set feedback onSQL&gt; create table aa(a number,b varchar2(20)); 表已创建。 SQL&gt; insert into aa values (3,'kasdf32'); 已创建 1 行。 SQL&gt; insert into aa values (null,'kasdf32'); 已创建 1 行。 SQL&...
【必知必会】COUNT(*) vs COUNT(col)
猿人谷
08-03 246
微信公众号：猿人谷 醍醐灌顶啊，给大家分享下。虽然是英文，但语法之类的都还比较简单，大家应该都看得懂的。覆盖索引(Covering Index )的文章。Looking...
count(*) vs count(column) vs count(1)
家山的专栏
03-13 648
概念 count(*)对行的数目进行计算，包含NULL count(column)对特定的列的值具有的行数进行计算，不包含NULL值。 count(1)这个用法和count(*)的结果是一样的。 Count(1) 实际上的意思是，评估Count（&lt;expression&gt;）中的表达式是否为NULL，如果为NULL则不计数，而非NULL则会计数。 Count（&lt;express...
深入分析：mysql统计条数count(*)、count(主键)、cout(1)、count(二级索引字段)、count(普通字段)性能比较
weixin_44625925的博客
07-06 1698
MyISAM 存储引擎（mysql5.5前）： count(*) 性能最佳，因为存储引擎会存储精确的行数，因此不采用其他写法。 InnoDB 存储引擎（mysql5.5后）： 先说结论，性能由高到低排序为： count(*) = count(最短非空索引字段) ≈ count(1) > count(比主键短的非空索引字段) > count(主键) > count(普通索引字段) > count(普通字段) 看到这个结论，可能有人会说卧槽 ，这是什么玩意，那么记住，任何情况都用coun
S7-1500 工艺模块 TM Count 2x24V 计数功能使用入门.docx
10-29
本文档详细介绍了 S7-1500 工艺模块 TM Count 2x24V 计数功能的使用入门。TM Count 2x24V 是一个能够提供双通道计数、测量以及位置反馈功能的工艺模块。该模块支持的编码器/信号类型包括 24 V 增量编码器、具有方向...
react-countup：around围绕CountUp.js的可配置React组件包装器
02-05
寻找v3.x文件？ 单击以获取以前的文档。 目录 安装 yarn add react-countup 用法 import CountUp from 'react-countup' ; 简单的例子 < CountUp xss=removed> 这将在渲染时开始从0到100向上计数过渡。 渲染道具...
关于 MySQL 百万数据量的 count(*) 查询如何优化？
热门推荐
码蹄疾
07-31 2万+
明确需求 对这个问题有兴趣是源于一次开发中遇到要统计人数的需求。类似于“得到”专栏的订阅数。 但是我的数据量比这个大很多，而对数据的准确性要求就不那么高。所以首先要明确需求。其他答案有的说了用缓存，有的答案对比了count(*)、count(1)的区别，都很好，但是我认为还是要看一下题主的场景。我根据我实际开发的经验总结如下几个方面，FYI。 数据量大/准确性要求低/请求量大 这种场景一般是...
Count(*)和Count(x_name)的区别
paomiange的专栏
03-28 338
sql的COUNT()函数用于查询记录数，主要有两种使用方式 1.COUNT(*)  返回的是所查表行数，它不会过滤掉null值和重复行 2.COUNT(x_name)  则会过滤掉null值，如果写成COUNT( DISTINCT x_name)就会过滤掉重复行，其中x_name就是你表中某一列的名字 很多人在用COUNT(1)，因为你的表中并不存在名为1的列，那么它其实和COUNT
[MySQL] count(*) vs count(1) vs count(column)
列苗
10-21 4905
MySQL版本：5.7.9数据表结构为： category: InnoDB 引擎，无索引CREATE TABLE `category` ( `id` int(11) NOT NULL AUTO_INCREMENT, `name` varchar(220) NOT NULL, `created_time` datetime NOT NULL, `updated_time` datet
java标签库 taglib pdf格式_JSTL——java标准标签库，java starand taglib
weixin_34877373的博客
02-16 109
02——JSTL1.java标准标签库，java starand taglib2.主要作用：用来替代jsp文件中的java代码一些逻辑判断if判断for循环3.一般是和EL 表达式结合使用4.语法应用1.在项目中引入jstl.jar和standard.jar2.在页面中使用taglib指定引入标签库3.在html代码中使用标准标签5.常用标签1.if判断java中的if(条件){}========...
JSTL-3
diaofenquan8810的博客
09-04 107
.循环标签：forEach标签， forTokens标签 <c:forEach>:标签:该标签根据循环条件遍历集合（Collection）中的元素 <c:forEach [var="变量名"] Items=“输出的集合” [varStatus="状态"][begin="从哪里开始"][end="从哪里结束"][step="步长"]></c:forEac...
JSP的学习（二）——EL和JSTL表达式
有问题请发邮箱dengyifanlittle@163.com进行讨论
10-06 721
一、EL表达式 ①基本概念 EL表达式: expression language表达式语言 EL（Expression Language） 是为了使JSP写起来更加简单。表达式语言的灵感来自于 ECMAScript 和 XPath 表达式语言，它提供了在 JSP 中简化表达式的方法，让Jsp的代码更加简化。把JSP中出现的相关的JAVA代码简化。 格式：${ EL表达式 }   等价于  ...
<c:forEach varStatus="status">中 varStatus的属性简介
Hello World!
01-10 2万+
我们常会用c标签来遍历需要的数据，为了方便使用，varStatus属性可以方便我们实现一些与行数相关的功能，如：奇数行、偶数行差异；最后一行特殊处理等等。先就varStatus属性常用参数总结下： ${status.index}      输出行号，从0开始。 ${status.count}      输出行号，从1开始。 ${status.current}   当前这次迭代的（集合中的）项
【六袆】JSP递增索引；JSP遍历list集合；JSP遍历springmvc传过来的集合；
六祎的博客
09-24 524
JSP递增序号 <!-- ${vs.count}序号从1开始 ${vs.index}序号从0开始 ${vs.last}最后一个序号 ${vs.first}第一个序号 --> <c:forEach items="${lis...
JSTL 标签大全详解
weixin_34413802的博客
11-23 1668
（尊重劳动成果，转载请注明出处：http://blog.csdn.net/qq_25827845/article/details/53311722 冷血之心的博客）一、JSTL标签介绍1、什么是JSTL？ JSTL是apache对EL表达式的扩展（也就是说JSTL依赖EL），JSTL是标签语言！JSTL标签使用以来非常方便，它与JSP动作标签一样，只不过它不是JSP内置的标签，...
JavaWeb基础知识day12——EL和JSTL以及JavaBean导航
心情舒畅
03-05 192
EL【Expression Language】 概述：EL(Expression Language) jsp的内置表达式语言,从jsp2.0开始 用来替代jsp的脚本 &lt;%=..%&gt; 格式:${el表达式} 作用: 1.获取域中数据 ★ 2.执行运算 ★ 3.获取常见的web对象 4.调用java的方法 获取域中数据:★ 注意:...
Te=X*TE_count*dt/sum(TE_count); TE_count(TE_count==0) = [];
最新发布
06-08
这段代码是Matlab代码，主要实现的功能是计算一组数据的加权平均值。...6. Te=X*TE_count*dt/sum(TE_count)计算加权平均值。 该代码适用于处理医学图像或者其他需要采用不同的权重进行加权平均的数据集合。
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值