mysql使用join和不使用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现在我将省略table变量create的计划，但两个查询的计划是相同的：

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)所以，简短的回答 - 除非每次维护它们时都花费很长时间来阅读它们，否则无需重写。