<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    On 05/29/2018 08:24 AM, Brian Bouterse wrote:<br>
    <blockquote type="cite"
cite="mid:CAAcvrTFDpj7gr-jSG-c4FR9D6T=x-O09uPUOzP4GXHTd31rN2A@mail.gmail.com">On
      Fri, May 25, 2018 at 7:39 PM, Dana Walker <span dir="ltr"><<a
          href="mailto:dawalker@redhat.com" target="_blank"
          moz-do-not-send="true">dawalker@redhat.com</a>></span>
      wrote:<br>
      <blockquote class="gmail_quote" style="margin:0 0 0
        .8ex;border-left:1px #ccc solid;padding-left:1ex">
        <div dir="ltr">I'm basically -1 for the reasons Jeff enumerated
          but if he is ok with this, I'm happy to go ahead with it.<br>
          <br>
          <blockquote class="gmail_quote" style="margin:0px 0px 0px
            0.8ex;border-left:1px solid
            rgb(204,204,204);padding-left:1ex">[Jeff]:<span class=""><br>
              <div>In classic relational modeling, using ID as the
                primary key is common practice.  Especially when ORMs
                are involved.  The "id" added by plugin writers is a
                natural key so naming it ID goes against convention.</div>
            </span></blockquote>
          <div><br>
          </div>
          <div>This is echoed here, for further reading (though perhaps
            this article is overly simplified for our needs) in the
            sections "Key Fields" and "Prefixes and Suffixes (are bad)":<br>
            <a
href="https://launchbylunch.com/posts/2014/Feb/16/sql-naming-conventions/"
              target="_blank" moz-do-not-send="true">https://launchbylunch.com/<wbr>posts/2014/Feb/16/sql-naming-<wbr>conventions/</a> 
            <br>
          </div>
        </div>
      </blockquote>
      <div><br>
      </div>
      <div>That is true, but this article also talks about avoiding
        reserved words as well. I think we're hearing 'id' is a commonly
        reserved word for content types being modeled by plugin writers.<br>
      </div>
      <div><br>
      </div>
    </blockquote>
    <br>
    The article[1] you mentioned states that 'ID' <i>should</i> be used
    for the PK which means it is inappropriate for natural key fields
    defined by plugin writers.  The reserved words caution in the
    article are DDL/DML reserved words "Ex: Avoid using words like <code>user</code>,
    <code>lock</code>, or <code>table</code>." not reserved by plugins.<br>
    <br>
    [1]
<a class="moz-txt-link-freetext" href="https://launchbylunch.com/posts/2014/Feb/16/sql-naming-conventions/#primary-keys">https://launchbylunch.com/posts/2014/Feb/16/sql-naming-conventions/#primary-keys</a><br>
  </body>
</html>