Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The back-references that Django produces are programatic, and do not affect the underlying Database schema. In other words, if you have a one-to-one or foreign key field on your Article pointing to your Revision, a column will be added to the Article table in the database, but not to the Revision table.</p> <p>Thus, removing the reverse relationship from the revision to the article is unnecessary. If you really feel strongly about it, and want to document in your code that the backlink is never used, a fairly common Django idiom is to give the fields a related_name attribute like <code>_unused_1</code>. So your Article model might look like the following:</p> <pre><code>class Article(models.Model): title = models.CharField(blank=False, max_length=80) slug = models.SlugField(max_length=80) revision_1 = models.OneToOneField(ArticleRevision, related_name='_unused_1') revision_2 = models.OneToOneField(ArticleRevision, related_name='_unused_2') def __unicode__(self): return self.title </code></pre> <p>That said, it's rare that a one-to-one relationship is actually useful in an application (unless you're optimizing for some reason) and I'd suggest carefully reviewing your DB schema to make sure this is really what you want. It may make sense to keep a single ForeignKey field on your ArticleRevision pointing back to an Article (since an ArticleRevision will, presumably, always need to be associated with an Article) and adding another column to Revision indicating whether it's published.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow to model one way one-to-one relationship in Django
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USmmalone
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow to model one way one-to-one relationship in Django
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COOne-to-one relationship is useful indeed, but in my case, the back-reference should already exist in the form of article-revisions reference and the additional references are just to mark direct references to currently published revision and currently edited revision.
      singulars
      1. PO
      1. USRoland Tepp
    2. COSince Django 1.2, related_name='+' will result in no backwards relation being available. https://docs.djangoproject.com/en/1.2/ref/models/fields/#django.db.models.ForeignKey.related_name
      singulars
      1. PO
      1. UStobych
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload