title: 【Django】Is writing all of the table definition in one model bad practice?
body: <p>I'm confused at Where I have to write table definition .
  Django have several apps and each app have models.
  Table definition is written in the models.
  However, table relationships is comprecated,so each app calls each other's model.It is comprecated and hard to find what app have a table.</p>
  
  <p>So,I want to put all of the table definition into one app.</p>
  
  <pre><code>project
   myapp
    models.py(just have business logics)    
    views.py
   common
     models.py(just table definition)
    views.py
  </code></pre>
  
  <p>This is simple and easy to understand,I think.
  Is this bad idea?</p>