Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You said, "ThreadedComment does not have a unique primary key of its own, relying on Object's promary [sic] key ('ID')." Django requires one field to be identified as a primary key. See <a href="http://docs.djangoproject.com/en/dev/topics/db/models/#automatic-primary-key-fields" rel="nofollow">Automatic primary key fields</a>.</p> <p><strong>More details . . .</strong></p> <p>The function pg_get_serial_sequence() returns the name of the sequence used by a specific column. So the following statement means, "Get the name of the sequence used for the 'id' column in the table 'threadedcomments_threadedcomment', set the sequence's last_value field to 1, and return 1 the next time nextval() is called.</p> <pre><code>SELECT setval(pg_get_serial_sequence('"threadedcomments_threadedcomment"','id'), 1, false); </code></pre> <p>But this statement</p> <pre><code>SELECT setval('"threadedcomments_threadedcomment_id_seq"', 1, false); </code></pre> <p>means, "Set the last_value field of the sequence named 'threadedcomments_threadedcomment_id_seq' to 1, and return 1 the next time nextval() is called."</p> <p>My guess is that the algorithm Django uses to name sequences changed between versions. I've seen other systems make similar changes because identifiers built up by concatenating table and column names became too long. I think Oracle identifiers have a 30-character limit; your identifier is 39 characters. I've seen Rails generate 70+ character identifiers, which break on PostgreSQL (63 or 64 character limit).</p>
    singulars
    1. This table or related slice is empty.
    1. PODjango tests failing after migrating to 1.2.5 - primary key issue for child model
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USMike Sherrill 'Cat Recall'
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. CO"Django requires one field to be identified as a primary key" - yes I know that but it used to work fine with the ID being in parent table, not the child table. It does not make any sense whatsoever to duplicate the ID in the child table as the relationship is one-to-one here. Should I just create a fake_id field with primary_key=True only to satisfy django? This sounds like a hirrible workaround.
      singulars
      1. PO
      1. USmichuk
    2. COI'd say you probably just need to set `primary_key=True` on parent_object. From the link I posted, "OneToOneField classes used to automatically become the primary key on a model. This is no longer true (although you can manually pass in the primary_key argument if you like)."
      singulars
      1. PO
      1. USMike Sherrill 'Cat Recall'
    3. COThe parent object had a primary_key=True already. This turned out to be a django bug. More details in my own answer to this question below.
      singulars
      1. PO
      1. USmichuk
 

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