Home > Database > Mysql Tutorial > Why is Mixing Implicit and Explicit JOINs in SQL Invalid Syntax?

Why is Mixing Implicit and Explicit JOINs in SQL Invalid Syntax?

Susan Sarandon
Release: 2025-01-14 19:37:47
Original
338 people have browsed it

Why is Mixing Implicit and Explicit JOINs in SQL Invalid Syntax?

Mixed implicit and explicit JOIN

Although this is an open question, mixing implicit and explicit JOINs in SQL results in invalid syntax. While explicit and implicit JOINs can work individually, combining them can lead to errors.

Consider the following example pattern:

<code class="language-sql">CREATE TABLE Employee (
    employeeID INT,
    name VARCHAR(255),
    managerEmployeeID INT   
)</code>
Copy after login

and sample data:

<code class="language-sql">INSERT INTO Employee (employeeID, name) VALUES (1, 'Gary')
INSERT INTO Employee (employeeID, name, managerEmployeeID) VALUES (2, 'Bob', 1)</code>
Copy after login

The following explicit JOIN query retrieves results as expected:

<code class="language-sql">SELECT e1.name,
       e2.name,
       e1Manager.name
  FROM Employee e1
 CROSS JOIN Employee e2
 INNER JOIN Employee e1Manager
    ON e1.managerEmployeeID = e1Manager.employeeID</code>
Copy after login

Similarly, this implicit JOIN query also works:

<code class="language-sql">SELECT e1.name,
       e2.name,
       e1Manager.name
  FROM Employee e1,
       Employee e2,
       Employee e1Manager
 WHERE e1.managerEmployeeID = e1Manager.employeeID</code>
Copy after login

Invalid SQL

However, when trying to mix implicit and explicit JOINs:

<code class="language-sql">SELECT e1.name, 
       e2.name, 
       e1Manager.name
  FROM Employee e1,
       Employee e2
 INNER JOIN Employee e1Manager 
    ON e1.managerEmployeeID = e1Manager.employeeID</code>
Copy after login

Errors will occur in both MSSQL 2000/2008 and MySQL. In MS2000 the error is:

<code>列前缀'e1'与查询中使用的表名或别名不匹配。</code>
Copy after login

In MySQL, the error is:

<code>'on'子句中未知列'e1.managerEmployeeID'。</code>
Copy after login

Why is this syntax invalid?

The SQL standard stipulates that the JOIN keyword has a higher priority than commas. However, table aliases can only be used after the corresponding table has been evaluated in the FROM clause.

In the mixed JOIN query, the JOIN...ON expression refers to e1, but e1 has not yet been evaluated because the comma-separated list of tables has not been processed yet.

Extra: Force Hibernate to use explicit JOIN

Unfortunately, my research into Hibernate's HQL documentation didn't turn up any information on how to force the use of explicit JOIN.

The above is the detailed content of Why is Mixing Implicit and Explicit JOINs in SQL Invalid Syntax?. For more information, please follow other related articles on the PHP Chinese website!

source:php.cn
Statement of this Website
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
Latest Articles by Author
Popular Tutorials
More>
Latest Downloads
More>
Web Effects
Website Source Code
Website Materials
Front End Template