使用Oracle中的查询替换列中的字符串(Replace string in a column using query in Oracle)

 并非所有选项都默认关闭。 在我们的文档（http://www.jshint.com/docs/）中，您可以看到一些选项是“执行”和一些“放松”[1]。 这意味着默认情况下会显示一些警告，您需要启用“放松”选项才能关闭它们。 
 
 现在，有了这些信息，让我们看看你的第二个问题： 
 
/*jshint eqeqeq:false, asi:false */
(function () { console.log(true == true); })()
 
 这段代码将触发一个不安全的比较警告，其中== true和缺少分号。 你试图通过关闭两个选项eqeqeq和asi来解决这个问题。 前者如果设置为true，则需要进行严格的比较，并且默认情况下会关闭，因此您可以忽略它。 你会得到一个警告，因为JSHint认为== true/false/0/null比较不安全，并且目前没有办法关闭它（例如，不会有警告a == b ）[2]。 后面的选项（asi）是一个放松的选项，所以你实际上需要打开它来告诉JSHint可以容忍丢失的分号。 所以为了让你的例子通过，你需要这样改变它： 
 
/*jshint asi:true */
(function () { console.log(true === true); }()
 
 [1] - 我知道这很混乱。 由于向后兼容，我不能只是改变选项的工作方式，但我正在努力减少混淆。 我将尽快为文档添加每个选项的默认值。 
 
 [2] - 即使没有相应的命名选项，即将发布的1.0.0版本将允许您忽略其代码的任何警告。 

Not all options are off by default. In our docs (http://www.jshint.com/docs/) you can see that some options are 'enforcing' and some 'relaxing'[1]. This means that some warnings will be displayed by default and you need to enable 'relaxing' option to turn them off.
 
Now, with this information, let's look at your second question:
 
/*jshint eqeqeq:false, asi:false */
(function () { console.log(true == true); })()
 
This code will trigger an unsafe comparison warning for == true and a missing semicolon. You tried to fix that by turning off two options eqeqeq and asi. The former, when set to true, requires strict comparison everywhere and is turned off by default so you can omit it. You get a warning because JSHint considers == true/false/0/null comparisons unsafe and currently there is no way to turn that off (there won't be warning for a == b for example)[2]. And the latter option (asi) is a relaxing option so you actually need to turn it on to tell JSHint that it's okay to tolerate missing semicolons. So to make your example pass you will need to change it this way:
 
/*jshint asi:true */
(function () { console.log(true === true); }()
 
[1] — I understand that this is confusing. Because of backwards compatibility I can't just change how options work but I'm working towards making it less confusing. I will add default values for each option to the docs soon-ish.
 
[2] — The upcoming 1.0.0 release will allow you to ignore any warnings by their code, even if there's no corresponding named option.