Question

I’m trying to store sections of a document in a Django app. The model looks like:

class Section(models.Model):
  project = models.ForeignKey(Project)
  parent_section = models.ForeignKey('Section', blank=True, null=True, related_name='child_set')
  predecessor_section = models.ForeignKey('Section', blank=True, null=True, related_name='predecessor_set')
  name = models.CharField(max_length=100)
  text = models.TextField(blank=True, null=True)

I create a whole lot of sections, link them (parent_section, predecessor_section) and store them by calling each of their save methods. However, when I look into the table after saving it, the parent_section_id and the predecessor_section_id are not set, even though I had objects attached to them before saving.

I assume it has to do with the fact that some parent_section instances don’t have an id assigned as their instance hasn’t been stored yet, but using manual transactions couldn’t solve the problem.

Any thoughts on that?

Cheers,
Max

Answer 1

objects do not have an id until you save them in Django ORM.

So I’d say you need to save() the object, then reference it in your parent/child sections (and re-save the sections).

However, another option to storing prec and next as pointers is to store an sequence_index (spaced by 10 to allow further inserts wiothout reordering) and order by this index.