<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>paulddraper</author><text>SQL doesn&amp;#x27;t say you can&amp;#x27;t use than name. All that a reserved word means is that you need to quote it to disambiguate.&lt;p&gt;&lt;pre&gt;&lt;code&gt;  CREATE TABLE &amp;quot;user&amp;quot; (
    id int PRIMARY KEY,
    name varchar(50) NOT NULL
  );
&lt;/code&gt;&lt;/pre&gt;
In fact, in this respect, SQL is much &lt;i&gt;better&lt;/i&gt; than most languages with their `clazz` and `klass` and `func`.</text><parent_chain><item><author>SPBS</author><text>SQL&amp;#x27;s most egregious reserved keyword is, in my opinion, &amp;quot;user&amp;quot;. Almost every application will have a users table. I gravitate towards singular table names these days [1], and SQL sitting its fat behind on the word &amp;quot;user&amp;quot; means I always have to defer to &amp;quot;users&amp;quot; just for the users table. There is almost no other keyword that I regularly run into conflict with other than &amp;quot;user&amp;quot;. I don&amp;#x27;t even use the &amp;quot;user&amp;quot; keyword in any SQL queries, what a terrible trade off.&lt;p&gt;[1] I used to prefer plural names, but now I favor singular names because no naming headaches with the plural intricacies of the English language.</text></item></parent_chain></comment><story><title>SQL reserved words – An empirical list</title><url>https://modern-sql.com/reserved-words-empirical-list</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>dpifke</author><text>Instead of picking a different name for your table, you can quote the table name in double quotes.&lt;p&gt;(&amp;quot;user&amp;quot; is what got me in the habit of doing this unconditionally, to the point where SQL with bare table&amp;#x2F;column names looks weird to me now.)</text><parent_chain><item><author>SPBS</author><text>SQL&amp;#x27;s most egregious reserved keyword is, in my opinion, &amp;quot;user&amp;quot;. Almost every application will have a users table. I gravitate towards singular table names these days [1], and SQL sitting its fat behind on the word &amp;quot;user&amp;quot; means I always have to defer to &amp;quot;users&amp;quot; just for the users table. There is almost no other keyword that I regularly run into conflict with other than &amp;quot;user&amp;quot;. I don&amp;#x27;t even use the &amp;quot;user&amp;quot; keyword in any SQL queries, what a terrible trade off.&lt;p&gt;[1] I used to prefer plural names, but now I favor singular names because no naming headaches with the plural intricacies of the English language.</text></item></parent_chain></comment><story><title>SQL reserved words – An empirical list</title><url>https://modern-sql.com/reserved-words-empirical-list</url></story>