mysql为什么可以不用join_在SQL或MySQL中不使用JOIN关键字的联接有问题吗？

在SQL Server中，总是有查询计划要检查，可以按以下方式进行文本输出：

SET SHOWPLAN_ALL ON

GO

DECLARE @TABLE_A TABLE

(

ID INT IDENTITY(1,1) NOT NULL PRIMARY KEY,

Data VARCHAR(10) NOT NULL

)

INSERT INTO @TABLE_A

SELECT 'ABC' UNION

SELECT 'DEF' UNION

SELECT 'GHI' UNION

SELECT 'JKL'

DECLARE @TABLE_B TABLE

(

ID INT IDENTITY(1,1) NOT NULL PRIMARY KEY,

Data VARCHAR(10) NOT NULL

)

INSERT INTO @TABLE_B

SELECT 'ABC' UNION

SELECT 'DEF' UNION

SELECT 'GHI' UNION

SELECT 'JKL'

SELECT A.Data, B.Data

FROM

@TABLE_A AS A, @TABLE_B AS B

WHERE

A.ID = B.ID

SELECT A.Data, B.Data

FROM

@TABLE_A AS A

INNER JOIN @TABLE_B AS B ON A.ID = B.ID

现在，我将省略为表变量创建的计划，尽管这两个查询的计划是相同的：

SELECT A.Data, B.Data  FROM   @TABLE_A AS A, @TABLE_B AS B  WHERE   A.ID = B.ID

|--Nested Loops(Inner Join, OUTER REFERENCES:([A].[ID]))

|--Clustered Index Scan(OBJECT:(@TABLE_A AS [A]))

|--Clustered Index Seek(OBJECT:(@TABLE_B AS [B]), SEEK:([B].[ID]=@TABLE_A.[ID] as [A].[ID]) ORDERED FORWARD)

SELECT A.Data, B.Data  FROM   @TABLE_A AS A   INNER JOIN @TABLE_B AS B ON A.ID = B.ID

|--Nested Loops(Inner Join, OUTER REFERENCES:([A].[ID]))

|--Clustered Index Scan(OBJECT:(@TABLE_A AS [A]))

|--Clustered Index Seek(OBJECT:(@TABLE_B AS [B]), SEEK:([B].[ID]=@TABLE_A.[ID] as [A].[ID]) ORDERED FORWARD)

因此，简短的答案-无需重写，除非您每次维护时都花很长时间尝试阅读它们？