Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Django's ORM does not implement an <a href="http://en.wikipedia.org/wiki/Identity_map" rel="noreferrer">identity map</a> (it's in the <a href="http://code.djangoproject.com/ticket/17" rel="noreferrer">ticket tracker</a>, but it isn't clear if or when it will be implemented; at least one core Django committer has <a href="http://spreadsheets.google.com/ccc?key=pSqnCvef6OXmGWQ9qbEVMeA" rel="noreferrer">expressed opposition to it</a>). This means that if you arrive at the same database object through two different query paths, you are working with different Python objects in memory.</p> <p>This means that your design (load everything into memory at once, modify a lot of things, then save it all back at the end) is unworkable using the Django ORM. First because it will often waste lots of memory loading in duplicate copies of the same object, and second because of "overwriting" issues like the one you're running into.</p> <p>You either need to rework your design to avoid these issues (either be careful to work with only one QuerySet at a time, saving anything modified before you make another query; or if you load several queries, look up all relations manually, don't ever traverse ForeignKeys using the convenient attributes for them), or use an alternative Python ORM that implements identity map. <a href="http://www.sqlalchemy.org/" rel="noreferrer">SQLAlchemy</a> is one option.</p> <p>Note that this doesn't mean Django's ORM is "bad." It's optimized for the case of web applications, where these kinds of issues are rare (I've done web development with Django for years and never once had this problem on a real project). If your use case is different, you may want to choose a different ORM.</p>
    singulars
    1. This table or related slice is empty.
    1. PODjango ORM: caching and manipulating ForeignKey objects
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCarl Meyer
    1. USCarl Meyer
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PODjango ORM: caching and manipulating ForeignKey objects
      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. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. CONicely summarized
      singulars
      1. PO
      1. USJarret Hardie
    2. COYes, thank you very much for this informative response. I know that it doesn't mean that Django's ORM is bad; in fact, I've developed an entire project using Django that doesn't require this sort of complicated data processing, and this issue has never come up, which is why I was at such a loss.
      singulars
      1. PO
      1. USBobby Moretti
 

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