Django

Code

Ticket #8946 (new)

Opened 2 months ago

Last modified 1 week ago

Denormalisation built in to the ORM

Reported by: simon Assigned to: nobody
Milestone: Component: Uncategorized
Version: 1.0 Keywords: djangocon
Cc: daevaorn@gmail.com Triage Stage: Unreviewed
Has patch: 0 Needs documentation: 0
Needs tests: 0 Patch needs improvement: 0

Description

Adrian and Jacob on stage at DjangoCon.

See also Cal's talk.

Attachments

Change History

09/10/08 13:34:57 changed by simon

  • needs_better_patch changed.
  • needs_tests changed.
  • needs_docs changed.

Some common denormalisations:

* A field maintains the count of a set of related fields, e.g. a forum Thread storing the number of Replies belonging to that thread. * A field is calculated from another field using an expensive operation. For example, rendering HTML using markdown. * A field from a joined table is frequently used for lookups, so is copied to the parent table to avoid having to make a join.

Please add more!

09/10/08 15:53:09 changed by Erik Allik <eallik@gmail.com>

In addition to the count of a set of related fields, also max/min/avg. For example one would want to store the creation date of the newest comment of an article because articles are often sorted by activity.

09/10/08 15:55:46 changed by mtredinnick

Contrary to Simon's request, let's please keep design discussion on the mailing list, as per normal. That way everybody can participate and there's a record. Tickets are terrible for design discussions. Yes, it might have to wait for a lull in other active conversations. Thankfully, we don't have to solve every problem in the next week or even the next month.

11/13/08 15:55:27 changed by alexkoshelev

  • cc set to daevaorn@gmail.com.

Add/Change #8946 (Denormalisation built in to the ORM)




Change Properties
Action