Oracle WHER条件的执行顺序是不是自右向左-Mysql Tutorial-php.cn

Home

Database

Mysql Tutorial

Oracle WHER条件的执行顺序是不是自右向左

WBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWB

Jun 07, 2016 pm 04:48 PM

突然在网上看到一种说法，ORACLE的WHERE条件执行顺序是自右向左的。理由是，当ORACLE的WHERE条件中出现多个00904表示符无效错误时

突然在网上看到一种说法，Oracle的WHERE条件执行顺序是自右向左的。

理由是，当ORACLE的WHERE条件中出现多个00904表示符无效错误时，错误是从右向左的顺序报的。

也有人提出解析顺序和执行顺序不是一码事，执行顺序要看执行计划。

于是，我特地作了个试验。

现做一个试验用表

SQL> select count(*) from dba_objects;

COUNT(*)
----------
72536

create table dba_objects2 as select * from dba_objects;

先来一次查询

SQL> select object_id,object_name from dba_objects2 where owner='HR' and object_id>500;

已选择41行。

执行计划
----------------------------------------------------------
Plan hash value: 4278809457

----------------------------------------------------------------------------------
| Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time |
----------------------------------------------------------------------------------
| 0 | SELECT STATEMENT | | 426 | 40896 | 283 (1)| 00:00:04 |
|* 1 | TABLE ACCESS FULL| DBA_OBJECTS2 | 426 | 40896 | 283 (1)| 00:00:04 |
----------------------------------------------------------------------------------

Predicate Information (identified by operation id):
---------------------------------------------------

1 - filter("OWNER"='HR' AND "OBJECT_ID">500)

Note
-----
- dynamic sampling used for this statement (level=2)

可以看出，这次Oracle是自左向右执行。那么SQL语句颠倒下会怎样？

SQL> select object_id,object_name from dba_objects2 where object_id>500 and owner='HR';

已选择41行。

执行计划
----------------------------------------------------------
Plan hash value: 4278809457

Predicate Information (identified by operation id):
---------------------------------------------------

1 - filter("OWNER"='HR' AND "OBJECT_ID">500)

Note
-----
- dynamic sampling used for this statement (level=2)

实际的执行顺序是自右向左。难道oracle的执行顺序是看开销的？把尽可能多缩小数据范围的条件放在前面执行。

为了证明自己的想法，我又增加了一个条件。

SQL> select object_id,object_name from dba_objects2 where object_id>500 and object_name like '%EM%' and owner='HR';

已选择14行。

执行计划
----------------------------------------------------------
Plan hash value: 4278809457

----------------------------------------------------------------------------------
| Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time |
----------------------------------------------------------------------------------
| 0 | SELECT STATEMENT | | 147 | 14112 | 283 (1)| 00:00:04 |
|* 1 | TABLE ACCESS FULL| DBA_OBJECTS2 | 147 | 14112 | 283 (1)| 00:00:04 |
----------------------------------------------------------------------------------

Predicate Information (identified by operation id):
---------------------------------------------------

1 - filter("OBJECT_NAME" IS NOT NULL AND "OWNER"='HR' AND
"OBJECT_ID">500 AND "OBJECT_NAME" LIKE '%EM%')

Note
-----
- dynamic sampling used for this statement (level=2)

ORACLE 智能的增加了"OBJECT_NAME" IS NOT NULL的条件，把放在中间的 OBJECT_NAME" LIKE '%EM%'放在了最后执行。

由此可见，，WHERE条件的执行顺序是按照开销的右小到大的顺序，智能调节的。

本文永久更新链接地址：

linux

Statement

The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn

MySQL: BLOB and other no-sql storage, what are the differences?May 13, 2025 am 12:14 AM

MySQL'sBLOBissuitableforstoringbinarydatawithinarelationaldatabase,whileNoSQLoptionslikeMongoDB,Redis,andCassandraofferflexible,scalablesolutionsforunstructureddata.BLOBissimplerbutcanslowdownperformancewithlargedata;NoSQLprovidesbetterscalabilityand

MySQL Add User: Syntax, Options, and Security Best PracticesMay 13, 2025 am 12:12 AM

ToaddauserinMySQL,use:CREATEUSER'username'@'host'IDENTIFIEDBY'password';Here'showtodoitsecurely:1)Choosethehostcarefullytocontrolaccess.2)SetresourcelimitswithoptionslikeMAX_QUERIES_PER_HOUR.3)Usestrong,uniquepasswords.4)EnforceSSL/TLSconnectionswith

MySQL: How to avoid String Data Types common mistakes?May 13, 2025 am 12:09 AM

ToavoidcommonmistakeswithstringdatatypesinMySQL,understandstringtypenuances,choosetherighttype,andmanageencodingandcollationsettingseffectively.1)UseCHARforfixed-lengthstrings,VARCHARforvariable-length,andTEXT/BLOBforlargerdata.2)Setcorrectcharacters

MySQL: String Data Types and ENUMs?May 13, 2025 am 12:05 AM

MySQloffersechar, Varchar, text, Anddenumforstringdata.usecharforfixed-Lengthstrings, VarcharerForvariable-Length, text forlarger text, AndenumforenforcingdataAntegritywithaetofvalues.

MySQL BLOB: how to optimize BLOBs requestsMay 13, 2025 am 12:03 AM

Optimizing MySQLBLOB requests can be done through the following strategies: 1. Reduce the frequency of BLOB query, use independent requests or delay loading; 2. Select the appropriate BLOB type (such as TINYBLOB); 3. Separate the BLOB data into separate tables; 4. Compress the BLOB data at the application layer; 5. Index the BLOB metadata. These methods can effectively improve performance by combining monitoring, caching and data sharding in actual applications.

Adding Users to MySQL: The Complete TutorialMay 12, 2025 am 12:14 AM

Mastering the method of adding MySQL users is crucial for database administrators and developers because it ensures the security and access control of the database. 1) Create a new user using the CREATEUSER command, 2) Assign permissions through the GRANT command, 3) Use FLUSHPRIVILEGES to ensure permissions take effect, 4) Regularly audit and clean user accounts to maintain performance and security.

Mastering MySQL String Data Types: VARCHAR vs. TEXT vs. CHARMay 12, 2025 am 12:12 AM

ChooseCHARforfixed-lengthdata,VARCHARforvariable-lengthdata,andTEXTforlargetextfields.1)CHARisefficientforconsistent-lengthdatalikecodes.2)VARCHARsuitsvariable-lengthdatalikenames,balancingflexibilityandperformance.3)TEXTisidealforlargetextslikeartic

MySQL: String Data Types and Indexing: Best PracticesMay 12, 2025 am 12:11 AM

Best practices for handling string data types and indexes in MySQL include: 1) Selecting the appropriate string type, such as CHAR for fixed length, VARCHAR for variable length, and TEXT for large text; 2) Be cautious in indexing, avoid over-indexing, and create indexes for common queries; 3) Use prefix indexes and full-text indexes to optimize long string searches; 4) Regularly monitor and optimize indexes to keep indexes small and efficient. Through these methods, we can balance read and write performance and improve database efficiency.

See all articles