blocks|key|1695659|text|这是我个人的方法。根据连接条件的长度，我有时会在下面的行缩进它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1695660|SELECT
++column1,
++column2
FROM
++table1
WHERE
++column3+IN+(+
++++SELECT+TOP(1)
++++++column4
++++FROM
++++++table2
++++++INNER+JOIN+table3+ON+table2.column1+=+table3.column1
++)


SELECT
++column1,
++column2
FROM
++table1
WHERE
++column3+IN+(+
++++SELECT+TOP(1)
++++++column4
++++FROM
++++++table2
++++++INNER+JOIN+table3
++++++++ON+table2.column1+=+table3.column1+--+for+long+ones
++)|code-block|syntax|javascript|1695661|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

This is my personal method. Depending on the length of the join condition I sometimes indent it on the line below.

<pre><code>SELECT
 column1,
 column2
FROM
 table1
WHERE
 column3 IN ( 
 SELECT TOP(1)
 column4
 FROM
 table2
 INNER JOIN table3 ON table2.column1 = table3.column1
 )


SELECT
 column1,
 column2
FROM
 table1
WHERE
 column3 IN ( 
 SELECT TOP(1)
 column4
 FROM
 table2
 INNER JOIN table3
 ON table2.column1 = table3.column1 -- for long ones
 )
</code></pre>

blocks|key|1695720|text|SELECT+column1,+column2
FROM+table
WHERE+column3+IN+(
++++SELECT+TOP(1)+column4
++++FROM+table2
++++INNER+JOIN+table3+ON+table2.column1+=+table3.column1
)|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|1695721|这篇文章很简短，很容易读懂。如果有更多的列被选择或者有更多的连接条件，我会做一些调整。|unstyled|1695722|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|J|8|@]|9|@]|A|$]]|$1|G|3|-4|5|F|7|K|8|@]|9|@]|A|$]]]|H|$]]

<pre><code>SELECT column1, column2
FROM table
WHERE column3 IN (
 SELECT TOP(1) column4
 FROM table2
 INNER JOIN table3 ON table2.column1 = table3.column1
)
</code></pre>

This is pretty short and easy to read. I'd make adjustments if there were more columns selected or more join conditions.

blocks|key|1695751|text|不确定是否有一个公认的做法，但现在我将如何做到这一点：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1695752|SELECT+
++++column1,+
++++column2+
FROM+
++++table1+
WHERE+
++++column3+IN+
++++(+
+++++SELECT+TOP(1)+
+++++++++column4+
+++++FROM+
+++++++++table2+
+++++++++INNER+JOIN+
+++++++++table3+
+++++++++++++ON+table2.column1+=+table3.column1+
++++)|code-block|syntax|javascript|1695753|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Not sure there is an accepted practice, but here's now how I'd do it:

<pre><code>SELECT 
 column1, 
 column2 
FROM 
 table1 
WHERE 
 column3 IN 
 ( 
 SELECT TOP(1) 
 column4 
 FROM 
 table2 
 INNER JOIN 
 table3 
 ON table2.column1 = table3.column1 
 )
</code></pre>

blocks|key|1695790|text|我通常做的是，|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1695791|print("SELECT+column1,+column2
+++++++FROM+table1
+++++++WHERE+column3+IN+(SELECT+TOP(1)+column4
+++++++++++++++++++++++++FROM+table2+INNER+JOIN+
++++++++++++++++++++++++++++++table3+ON+table2.column1+=+table3.column1)");|code-block|syntax|javascript|1695792|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

What I usually do is,

<pre><code>print("SELECT column1, column2
 FROM table1
 WHERE column3 IN (SELECT TOP(1) column4
 FROM table2 INNER JOIN 
 table3 ON table2.column1 = table3.column1)");
</code></pre>

blocks|key|1695827|text|当然，这可以归结为个人喜好。如果是在团队环境中，为了保持一致性，应该在成员之间达成一致。但这将是我的偏好：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1695828|SELECT+column1,+column2
FROM+++table1
WHERE++column3+IN(SELECT+++++TOP(1)+column4
++++++++++++++++++FROM+++++++table2
++++++++++++++++++INNER+JOIN+table3+ON
+++++++++++++++++++++++++++++table2.column1+=+table3.column1
+++++++++++++++++)|code-block|syntax|javascript|1695829|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Of course, this comes down to personal preference. And if in a team setting, it's something that should be agreed upon among the members for consistency's sake. But this would be my preference:

<pre><code>SELECT column1, column2
FROM table1
WHERE column3 IN(SELECT TOP(1) column4
 FROM table2
 INNER JOIN table3 ON
 table2.column1 = table3.column1
 )
</code></pre>

blocks|key|1480705|text|我的格式如下：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1480706|SELECT
++++column1,+
++++column2
FROM+
++++table1
WHERE+
++++column3+IN+(SELECT+TOP(1)+
++++++++++++++++++++column4+
++++++++++++++++FROM+
++++++++++++++++++++table2+
++++++++++++++++++++INNER+JOIN+table3+ON+table2.column1+=+table3.column1)|code-block|syntax|javascript|1480707|或者像这样：|1480708|SELECT
++++column1,+
++++column2
FROM+
++++table1
WHERE+
++++column3+IN+(SELECT+TOP(1)+column4+
++++++++++++++++FROM+table2+
++++++++++++++++INNER+JOIN+table3+ON+table2.column1+=+table3.column1)|1480709|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

I would format like this:

<pre><code>SELECT
 column1, 
 column2
FROM 
 table1
WHERE 
 column3 IN (SELECT TOP(1) 
 column4 
 FROM 
 table2 
 INNER JOIN table3 ON table2.column1 = table3.column1)
</code></pre>

or like this:

<pre><code>SELECT
 column1, 
 column2
FROM 
 table1
WHERE 
 column3 IN (SELECT TOP(1) column4 
 FROM table2 
 INNER JOIN table3 ON table2.column1 = table3.column1)
</code></pre>

blocks|key|1480780|text|我不知道是否有一个标准，但我喜欢这样做；|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1480781|SELECT+column1,+column2
++FROM+table1
WHERE+column3+IN
(
++++SELECT+TOP(1)+column4
++++++FROM+table2
++++INNER+JOIN+table3
++++++ON+table2.column1+=+table3.column1
)|code-block|syntax|javascript|1480782|因为我可以更好地阅读和分析SQL。|1480783|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I don't know if there's a standard but I like to do it this way;

<pre><code>SELECT column1, column2
 FROM table1
WHERE column3 IN
(
 SELECT TOP(1) column4
 FROM table2
 INNER JOIN table3
 ON table2.column1 = table3.column1
)
</code></pre>

because I can read and analyze the SQL better.

blocks|key|1480802|text|我喜欢在代码中有“河流”的空白。这使得它更容易扫描。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1480803|SELECT+column1,
+++++++column2
++FROM+table1
+WHERE+column3+IN+(SELECT+column4
+++++++++++++++++++++FROM+table2
+++++++++++++++++++++JOIN+table3
+++++++++++++++++++++++ON+table2.column1+=+table3.column1);|code-block|syntax|javascript|1480804|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I like to have "rivers" of white space in the code. It makes it a little easier to scan.

<pre><code>SELECT column1,
 column2
 FROM table1
 WHERE column3 IN (SELECT column4
 FROM table2
 JOIN table3
 ON table2.column1 = table3.column1);
</code></pre>

blocks|key|1480845|text|这是我的正常偏好：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1480846|++++SELECT+column1
++++++++,column2
++++FROM+table1
++++WHERE+column3+IN+(
++++++++SELECT+TOP(1)+column4
++++++++FROM+table2
++++++++INNER+JOIN+table3
++++++++++++ON+table2.column1+=+table3.column1
++++)|code-block|syntax|javascript|1480847|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

This is my normal preference:

<pre><code> SELECT column1
 ,column2
 FROM table1
 WHERE column3 IN (
 SELECT TOP(1) column4
 FROM table2
 INNER JOIN table3
 ON table2.column1 = table3.column1
 )
</code></pre>

blocks|key|1696016|text|这是一个品味问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1696017|这是我的偏好。|1696018|SELECT+
++column1
+,column2
FROM
++table1
WHERE+column3+IN+(
+++++++++++++++++SELECT+TOP(1)+column4
+++++++++++++++++FROM+
+++++++++++++++++++table2
+++++++++++++++++++INNER+JOIN+table3
+++++++++++++++++ON+table2.column1+=+table3.column1
+++++++++++++++++)|code-block|syntax|javascript|1696019|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

This is a matter of taste.

This is my preference.

<pre><code>SELECT 
 column1
 ,column2
FROM
 table1
WHERE column3 IN (
 SELECT TOP(1) column4
 FROM 
 table2
 INNER JOIN table3
 ON table2.column1 = table3.column1
 )
</code></pre>

blocks|key|1696059|text|我喜欢让我的查询的不同部分垂直排列。对于SQL，我倾向于使用8个空格的制表符大小，这似乎工作得很好。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1696060|SELECT++column1,+
++++++++column2
FROM++++table1
WHERE+++column3+IN
(
++++++++SELECT+TOP(1)+column4
++++++++FROM++++table2
++++++++INNER+JOIN+table3
++++++++ON++++++table2.column1++=+table3.column1
)|code-block|syntax|javascript|1696061|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I like to have the different parts of my query line up vertically. I tend to use a tab size of 8 spaces for SQL which seems to work well.

<pre><code>SELECT column1, 
 column2
FROM table1
WHERE column3 IN
(
 SELECT TOP(1) column4
 FROM table2
 INNER JOIN table3
 ON table2.column1 = table3.column1
)
</code></pre>

blocks|key|1480985|text|SQL格式化是一个存在大量差异和分歧的领域……但是，我喜欢把重点放在可读性上，并认为无论你做什么，始终如一地遵守任何降低可读性的规则都是“愚蠢的一致性”(“愚蠢的一致性对于简单的头脑来说是一个怪物”)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1480986|因此，这里有一些指导原则，而不是称之为规则。对于SQL语句中的每个主要子句(Select、Insert、Delete、From、Where、Having、Group+BY、Order+By、...我可能遗漏了一些)应该很容易识别。因此，我通常在最高级别缩进它们，所有这些都是相互缩进的。然后在每个子句中，我均匀地缩进下一个逻辑子结构...以此类推..但如果在任何个别情况下这样做更具可读性，我可以自由地(并且经常这样做)更改模式……复杂的Case语句就是一个很好的例子。因为任何需要水平滚动的东西都会极大地降低可读性，所以我经常在多行上编写复杂的(嵌套的)+Case表达式。当我这样做的时候，我试着根据它在SQL语句中的逻辑位置来保持这样的语句的开头挂起缩进，并将其余的语句行进一步缩进几个字符。|1480987|SQL数据库代码已经存在很长一段时间了，因为在计算机之前有小写，所以历史上有对大写关键字的偏好，但我更喜欢可读性而不是传统...(不管怎样，我现在使用的每个工具都用颜色对关键词进行了编码)|1480988|我还将使用表别名来减少为了理解查询结构而必须扫描的文本的数量，只要别名不会造成混淆。在少于3个或4个表的查询中，单字符别名就可以了，如果所有其他表都以不同的字母开头，我通常使用表的第一个字母...同样，最有助于提高可读性的就是它。最后，如果您的数据库支持它，那么许多关键字都是可选的(如别名的“内部”、“外部”、"As“等)。"Into“(from+Insert+Into)在Sql+Server上是可选的-但在Oracle上不是)，所以如果您的代码需要独立于平台，请谨慎使用它……|1480989|你的例子，我会写成：|1480990|Select+column1,+column2
From+table1+T1
Where+column3+In+(Select+Top(1)+column4
++++++++++++++++++From+table2+T2
+++++++++++++++++++++Join+table3+T3
+++++++++++++++++++++++++On+T2.column1+=+T3.column1)|code-block|syntax|javascript|1480991|或|1480992|Select+column1,+column2
From+table1+T1
Where+column3+In+
+++++(Select+Top(1)+column4
++++++From+table2+T2
+++++++++Join+table3+T3
++++++++++++On+T2.column1+=+T3.column1)|1480993|如果select子句上还有更多的列，我将缩进第二行和后续行...我通常不遵守任何严格的规则(每行一列)，因为垂直滚动几乎和水平滚动一样不利于可读性，特别是当屏幕的前十列中有任何文本时)|1480994|Select+column1,+column2,+Col3,+Col4,+column5,
++++column6,+Column7,+isNull(Column8,+'FedEx')+Shipper,
++++Case+Upper(Column9)+
+++++++When+'EAST'++Then+'JFK'
+++++++When+'SOUTH'+Then+'ATL'
+++++++When+'WEST'++Then+'LAX'
+++++++When+'NORTH'+Then+'CHI'+End+HubPoint
From+table1+T1
Where+column3+In+
+++++(Select+Top(1)+column4
++++++From+table2+T2
+++++++++Join+table3+T3
++++++++++++On+T2.column1+=+T3.column1)|1480995|以使代码最具可读性的方式格式化代码。|1480996|entityMap^0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|11|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|12|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|13|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|14|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|15|8|@]|9|@]|A|$M|N]]|$1|O|3|P|5|6|7|16|8|@]|9|@]|A|$]]|$1|Q|3|R|5|L|7|17|8|@]|9|@]|A|$M|N]]|$1|S|3|T|5|6|7|18|8|@]|9|@]|A|$]]|$1|U|3|V|5|L|7|19|8|@]|9|@]|A|$M|N]]|$1|W|3|X|5|6|7|1A|8|@]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]]|Z|$]]

SQL formatting is an area where there is a great deal of variance and disagreement... But fwiw, I like to focus on readability and think that whatever you do, consistently conforming to any rules that reduce readability is, as the old cliche goes, a "foolish consistency" ( "Foolish consistency is a hobgoblin for simple minds" ) 

So, instead of calling them rules, here are some guidelines.
For each Major clause in a SQL statement (Select, Insert, Delete, From, Where, Having, Group BY, Order By, ... I may be missing a few) should be EASILY identifiable. So I generally indent them at the highest level, all even with each other. Then within each clause, I indent the next logical sub structure evenly... and so on.. But I feel free to (and often do) change the pattern if in any individual case it would be more readable to do so... Complex Case statements are a good example. Because anything that requires horizontal scrolling reduces readability enormously, I often write complex (nested) Case expressions on multiple lines. When I do, I try to keep the beginning of such a statement hanging indent based on it's logical place in the SQL statement, and indent the rest of the statement lines a few characters furthur... 

SQL Database code has been around for a long time, since before computers had lower case, so there is a historical preference for upper casing keywords, but I prefer readability over tradition... (and every tool I use color codes the key words now anyway)

I also would use Table aliases to reduce the amount of text the eye has to scan in order to grok the structure of the query, as long as the aliases do not create confusion. In a query with less than 3 or 4 tables, Single character aliases are fine, I often use first letter of the table if all ther tables start with a different letter... again, whatever most contributes to readability. Finally, if your database supports it, many of the keywords are optional, (like "Inner", "Outer", "As" for aliases, etc.) "Into" (from Insert Into) is optional on Sql Server - but not on Oracle) So be careful about using this if your code needs to be platform independant... 

Your example, I would write as:

<pre><code>Select column1, column2
From table1 T1
Where column3 In (Select Top(1) column4
 From table2 T2
 Join table3 T3
 On T2.column1 = T3.column1)
</code></pre>

Or

<pre><code>Select column1, column2
From table1 T1
Where column3 In 
 (Select Top(1) column4
 From table2 T2
 Join table3 T3
 On T2.column1 = T3.column1)
</code></pre>

If there many more columns on the select clause, I would indent the second and subsequent lines... I generally do NOT adhere to any strict (one column per row) kind of rule as scrolling veritcally is almost as bad for readability as scrolling horizontally is, especially if only the first ten columns of the screen have any text in them)

<pre><code>Select column1, column2, Col3, Col4, column5,
 column6, Column7, isNull(Column8, 'FedEx') Shipper,
 Case Upper(Column9) 
 When 'EAST' Then 'JFK'
 When 'SOUTH' Then 'ATL'
 When 'WEST' Then 'LAX'
 When 'NORTH' Then 'CHI' End HubPoint
From table1 T1
Where column3 In 
 (Select Top(1) column4
 From table2 T2
 Join table3 T3
 On T2.column1 = T3.column1)
</code></pre>

Format the code in whatever manner makes it the most readable...

blocks|key|1696182|text|我喜欢jalbert将关键词排列在右边的形式。我还想补充说，我喜欢左边的and和on+(有些人把它们放在右边)。此外，我喜欢在可能的情况下对齐我的等号。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1696183|SELECT+column1,+
+++++++column2++
++FROM+table1,+table2+
+WHERE+table1.column1+=+table2.column4+
+++AND+table1.col5++++=+"hi"+
++++OR+table2.myfield+=+678+|code-block|syntax|javascript|1696184|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I like jalbert's form of lining up the keywords on their right. I'd also add that I like the ANDs and ORs on the left (some people put them on the right.) In addition, I like to line up my equals signs when possible.

<pre><code>
SELECT column1, 
 column2 
 FROM table1, table2 
 WHERE table1.column1 = table2.column4 
 AND table1.col5 = "hi" 
 OR table2.myfield = 678 
</code></pre>

blocks|key|1696225|text|我已经为我们的商店写了一个代码标准，它极端偏向于可读性/“可发现性”(后者主要用于插入-选择语句)：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1696226|SELECT+
++++column1,+
++++column2
FROM+
++++table1
WHERE+
++++column3+IN
++++(
++++++++SELECT+TOP(1)+
++++++++++++column4
++++++++FROM+
++++++++++++table2
++++++++++++INNER+JOIN+table3+ON+table2.column1+=+table3.column1
++++)|code-block|syntax|javascript|1696227|在更复杂的查询中，它的用处变得更加明显：|1696228|SELECT
++++Column1,
++++Column2,
++++Function1
++++(
++++++++Column1,
++++++++Column2
++++)+as+Function1,
++++CASE
++++WHEN+Column1+=+1+THEN
++++++++a
++++ELSE
++++++++B
++++END+as+Case1+++++++
FROM
++++Table1+t1
++++INNER+JOIN+Table2+t2+ON+t1.column12+=+t2.column21
WHERE
++++(
++++++++FilterClause1
++++++++AND+FilterClause2
++++)
++++OR
++++(
++++++++FilterClause3
++++++++AND+FilterClause4
++++)|1696229|一旦您在大多数查询中迁移到具有多个连接的系统，我的经验是，自由地使用垂直空间是您处理复杂SQL的最好朋友。|1696230|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

I've written a code standard for our shop that is biased in the extreme towards readability/"discoverability" (the latter being primarily useful in insert-select statements):

<pre><code>SELECT 
 column1, 
 column2
FROM 
 table1
WHERE 
 column3 IN
 (
 SELECT TOP(1) 
 column4
 FROM 
 table2
 INNER JOIN table3 ON table2.column1 = table3.column1
 )
</code></pre>

On more complex queries it becomes more obvious how this is useful:

<pre><code>SELECT
 Column1,
 Column2,
 Function1
 (
 Column1,
 Column2
 ) as Function1,
 CASE
 WHEN Column1 = 1 THEN
 a
 ELSE
 B
 END as Case1 
FROM
 Table1 t1
 INNER JOIN Table2 t2 ON t1.column12 = t2.column21
WHERE
 (
 FilterClause1
 AND FilterClause2
 )
 OR
 (
 FilterClause3
 AND FilterClause4
 )
</code></pre>

Once you move to systems with more than a single join in most of your queries, it has been my experience that using vertical space liberally is your best friend with complex SQL.

blocks|key|1696305|text|如果您想重新格式化一个冗长的SQL语句，而不想进行所有的键入和跳转操作，那么可以将其放入this+website中，并获得格式化良好的结果。您可以尝试各种格式，看看哪种格式使您的文本最具可读性。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1696306|编辑:我相信this是2014年的SQL格式化程序的位置。|1696307|entityMap|0|LINK|mutability|MUTABLE|url|http://www.orafaq.com/cgi-bin/sqlformat/pp/utilities/sqlformatter.tpl|1|http://sqlformat.org/^0|18|C|0|0|6|4|1|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@$A|U|B|V|1|W]]|C|$]]|$1|F|3|-4|5|6|7|X|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]]]

If you have a lengthy SQL statement that you'd like to reformat without all the typing and tabbing, you can slap it into <a href="http://www.orafaq.com/cgi-bin/sqlformat/pp/utilities/sqlformatter.tpl" rel="nofollow noreferrer">this website</a> and get a nicely formatted result. You can experiment with various formats to see which makes your text the most readable.

Edit: I believe that <a href="http://sqlformat.org/" rel="nofollow noreferrer">this</a> is the 2014 location of the SQL formatter.

blocks|key|1696364|text|我刚刚把它放进我的SQL美化程序，结果是这样的……|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1696365|SELECT+column1,+column2
FROM+table1
WHERE+column3+IN
(
SELECT+TOP(1)+column4
++++FROM+table2
++++++++++++INNER+JOIN+table3
++++++++++++ON+table2.column1+=+table3.column1
)|code-block|syntax|javascript|1696366|http://extras.sqlservercentral.com/prettifier/prettifier.aspx|offset|length|1696367|.....But我还没有想出一种将颜色带入StackOverflow的方法。|1696368|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|0|1P|0|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|U|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|V|8|@]|9|@$I|W|J|X|1|Y]]|A|$]]|$1|K|3|L|5|6|7|Z|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|H]]]]

I've just put it through my SQL prettifier and it came out like this....

<pre><code>SELECT column1, column2
FROM table1
WHERE column3 IN
(
SELECT TOP(1) column4
 FROM table2
 INNER JOIN table3
 ON table2.column1 = table3.column1
)
</code></pre>

<a href="http://extras.sqlservercentral.com/prettifier/prettifier.aspx" rel="nofollow noreferrer">http://extras.sqlservercentral.com/prettifier/prettifier.aspx</a>

.....But I haven't worked out a way of getting colours into StackOverflow.

blocks|key|1696383|text|缩进一个非常复杂的SQL的例子：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1696384|SELECT+
++++produtos_cesta.cod_produtos_cesta,+
++++produtos.nome_pequeno,
++++tab_contagem.cont,
++++produtos_cesta.sku,+
++++produtos_kits.sku_r+AS+sku_kit,+
++++sku_final+=+CASE
++++++++WHEN+produtos_kits.sku_r+IS+NOT+NULL+THEN+produtos_kits.sku_r
++++++++ELSE+produtos_cesta.sku
++++END,
++++estoque+=+CASE
++++++++WHEN+produtos2.estoque+IS+NOT+NULL+THEN+produtos2.estoque
++++++++ELSE+produtos.estoque
++++END,
++++produtos_cesta.unidades+as+unidades1,+
++++unidades_x_quantidade+=+CASE
++++++++WHEN+produtos.cod_produtos_kits_tipo+=+1+THEN+CAST(produtos_cesta.quantidade+*+(produtos_cesta.unidades+/+tab_contagem.cont)+*+produtos_kits.quantidade+AS+int)
++++++++ELSE+CAST(produtos_cesta.quantidade+*+produtos_cesta.unidades+AS+int)
++++END,
++++unidades+=+CASE
++++++++WHEN+produtos.cod_produtos_kits_tipo+=+1+THEN+produtos_cesta.unidades+/+tab_contagem.cont+*+produtos_kits.quantidade
++++++++ELSE+produtos_cesta.unidades
++++END,
++++unidades_parent+=+produtos_cesta.unidades,
++++produtos_cesta.quantidade,
++++produtos.controla_estoque,+
++++produtos.status
FROM+
++++produtos_cesta+
INNER+JOIN+produtos+
++++ON+(produtos_cesta.sku+=+produtos.sku)+
INNER+JOIN+produtos_pacotes+
++++ON+(produtos_cesta.sku+=+produtos_pacotes.sku)+
INNER+JOIN+(
++++SELECT+
++++++++produtos_cesta.cod_produtos_cesta,
++++++++cont+=+SUM(
++++++++++++CASE
++++++++++++++++WHEN+produtos_kits.quantidade+IS+NOT+NULL+THEN+produtos_kits.quantidade
++++++++++++++++ELSE+1
++++++++++++END
++++++++)
++++FROM+
++++++++produtos_cesta+
++++LEFT+JOIN+produtos_kits+
++++++++ON+(produtos_cesta.sku+=+produtos_kits.sku)+
++++LEFT+JOIN+produtos+
++++++++ON+(produtos_cesta.sku+=+produtos.sku)+
++++WHERE+
++++++++shopper_id+=+'"+%2B+mscsShopperId+%2B+@"'+
++++GROUP+BY+
++++++++produtos_cesta.cod_produtos_cesta,+
++++++++produtos_cesta.sku,+
++++++++produtos_cesta.unidades+
)+
AS+tab_contagem
++++ON+(produtos_cesta.cod_produtos_cesta+=+tab_contagem.cod_produtos_cesta)
LEFT+JOIN+produtos_kits+
++++ON+(produtos.sku+=+produtos_kits.sku)+
LEFT+JOIN+produtos+as+produtos2
++++ON+(produtos_kits.sku_r+=+produtos2.sku)+
WHERE+
++++shopper_id+=+'"+%2B+mscsShopperId+%2B+@"'+
GROUP+BY+
++++produtos_cesta.cod_produtos_cesta,+
++++tab_contagem.cont,
++++produtos_cesta.sku,+
++++produtos_kits.sku_r,+
++++produtos.cod_produtos_kits_tipo,+
++++produtos2.estoque,
++++produtos.controla_estoque,+
++++produtos.estoque,+
++++produtos.status,+
++++produtos.nome_pequeno,+
++++produtos_cesta.unidades,+
++++produtos_cesta.quantidade,
++++produtos_kits.quantidade
ORDER+BY+
++++produtos_cesta.sku,+
++++produtos_cesta.unidades+DESC|code-block|syntax|javascript|1696385|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Example indenting a very very very complex SQL:

<pre><code>SELECT 
 produtos_cesta.cod_produtos_cesta, 
 produtos.nome_pequeno,
 tab_contagem.cont,
 produtos_cesta.sku, 
 produtos_kits.sku_r AS sku_kit, 
 sku_final = CASE
 WHEN produtos_kits.sku_r IS NOT NULL THEN produtos_kits.sku_r
 ELSE produtos_cesta.sku
 END,
 estoque = CASE
 WHEN produtos2.estoque IS NOT NULL THEN produtos2.estoque
 ELSE produtos.estoque
 END,
 produtos_cesta.unidades as unidades1, 
 unidades_x_quantidade = CASE
 WHEN produtos.cod_produtos_kits_tipo = 1 THEN CAST(produtos_cesta.quantidade * (produtos_cesta.unidades / tab_contagem.cont) * produtos_kits.quantidade AS int)
 ELSE CAST(produtos_cesta.quantidade * produtos_cesta.unidades AS int)
 END,
 unidades = CASE
 WHEN produtos.cod_produtos_kits_tipo = 1 THEN produtos_cesta.unidades / tab_contagem.cont * produtos_kits.quantidade
 ELSE produtos_cesta.unidades
 END,
 unidades_parent = produtos_cesta.unidades,
 produtos_cesta.quantidade,
 produtos.controla_estoque, 
 produtos.status
FROM 
 produtos_cesta 
INNER JOIN produtos 
 ON (produtos_cesta.sku = produtos.sku) 
INNER JOIN produtos_pacotes 
 ON (produtos_cesta.sku = produtos_pacotes.sku) 
INNER JOIN (
 SELECT 
 produtos_cesta.cod_produtos_cesta,
 cont = SUM(
 CASE
 WHEN produtos_kits.quantidade IS NOT NULL THEN produtos_kits.quantidade
 ELSE 1
 END
 )
 FROM 
 produtos_cesta 
 LEFT JOIN produtos_kits 
 ON (produtos_cesta.sku = produtos_kits.sku) 
 LEFT JOIN produtos 
 ON (produtos_cesta.sku = produtos.sku) 
 WHERE 
 shopper_id = '" + mscsShopperId + @"' 
 GROUP BY 
 produtos_cesta.cod_produtos_cesta, 
 produtos_cesta.sku, 
 produtos_cesta.unidades 
) 
AS tab_contagem
 ON (produtos_cesta.cod_produtos_cesta = tab_contagem.cod_produtos_cesta)
LEFT JOIN produtos_kits 
 ON (produtos.sku = produtos_kits.sku) 
LEFT JOIN produtos as produtos2
 ON (produtos_kits.sku_r = produtos2.sku) 
WHERE 
 shopper_id = '" + mscsShopperId + @"' 
GROUP BY 
 produtos_cesta.cod_produtos_cesta, 
 tab_contagem.cont,
 produtos_cesta.sku, 
 produtos_kits.sku_r, 
 produtos.cod_produtos_kits_tipo, 
 produtos2.estoque,
 produtos.controla_estoque, 
 produtos.estoque, 
 produtos.status, 
 produtos.nome_pequeno, 
 produtos_cesta.unidades, 
 produtos_cesta.quantidade,
 produtos_kits.quantidade
ORDER BY 
 produtos_cesta.sku, 
 produtos_cesta.unidades DESC
</code></pre>

blocks|key|1481238|text|SELECT
++++Column1,
++++Column2
FROM
++++Table1
WHERE
++++Column3+IN
++++(
++++++++SELECT+TOP+(1)
++++++++++++Column4
++++++++FROM+
++++++++++++Table2
++++++++INNER+JOIN+
++++++++++++Table3
++++++++ON
++++++++++++Table2.Column1+=+Table3.Column1
++++)|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|1481239|unstyled|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$B|C]]|$1|D|3|-4|5|E|7|H|8|@]|9|@]|A|$]]]|F|$]]

<pre><code>SELECT
 Column1,
 Column2
FROM
 Table1
WHERE
 Column3 IN
 (
 SELECT TOP (1)
 Column4
 FROM 
 Table2
 INNER JOIN 
 Table3
 ON
 Table2.Column1 = Table3.Column1
 )
</code></pre>

blocks|key|1696457|text|由于上面的大多数都排列了返回列名，我发现排列表名和条件对可读性有很大帮助。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1696458|SELECT+
++++column1,+
++++column2
FROM+
++++table1
WHERE+
++++column3+IN
++++(
++++++++SELECT+TOP(1)+
++++++++++++column4
++++++++FROM+
++++++++++++table2+INNER+JOIN+
++++++++++++table3+ON+table2.column1+=+table3.column1
++++)|code-block|syntax|javascript|1696459|以及当连接条件变得很长时。|1696460|SELECT
++++Column1,
++++Column2
FROM+
++++Table1+JOIN+
++++Table2+ON+
++++++++Table1.Column3+=+Table2.Column4+JOIN+
++++Table3+ON+
++++++++Table2.Column1+=+Table3.Column1+and
++++++++Table2.ColumnX+=+@x+and
++++++++Table3.ColumnY+=+@y
WHERE
++++Condition1=xxx+and
++++Condition2=yyy+and
++++(
++++++++Condition3=aaa+or
++++++++Condition4=bbb
++++)|1696461|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

As most above have lined up the return column names, I find lining up tables names and conditions helps readability a lot.

<pre><code>SELECT 
 column1, 
 column2
FROM 
 table1
WHERE 
 column3 IN
 (
 SELECT TOP(1) 
 column4
 FROM 
 table2 INNER JOIN 
 table3 ON table2.column1 = table3.column1
 )
</code></pre>

And for when join conditions get long.

<pre><code>SELECT
 Column1,
 Column2
FROM 
 Table1 JOIN 
 Table2 ON 
 Table1.Column3 = Table2.Column4 JOIN 
 Table3 ON 
 Table2.Column1 = Table3.Column1 and
 Table2.ColumnX = @x and
 Table3.ColumnY = @y
WHERE
 Condition1=xxx and
 Condition2=yyy and
 (
 Condition3=aaa or
 Condition4=bbb
 )
</code></pre>

What is the accepted practice for indenting SQL statements? For example, consider the following SQL statement:

<pre><code>SELECT column1, column2
FROM table1
WHERE column3 IN
(
SELECT TOP(1) column4
FROM table2
INNER JOIN table3
ON table2.column1 = table3.column1
)
</code></pre>

How should this be indented? Many thanks.

SQL Statement indentation good practice

SQL数据库

数据库

缩进SQL语句的公认实践是什么？例如，考虑以下SQL语句：SELECT column1, column2FROM table1WHERE column3 IN(SELECT TOP(1) column4FROM table2INNER JOIN table3ON table2.column1 = table3.colu...

问SQL语句缩进的良好实践
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问SQL语句缩进的良好实践EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问SQL语句缩进的良好实践
EN