Learnings

<p>In Postgres, "empty updates" have the same cost per row as any other update. Even if the values won't change after the <code>UPDATE</code>, the operation will still have the same performance: </p>

<p>Using window functions on Django ORM </p>

<p>django-pgtrigger provides primitives for configuring Postgres triggers on Django models without raw SQL in many cases: </p>

<p>Django Generic Functionality without Generic Relations: </p>

<p>django-raw-sugar: Turns your raw SQL into a QuerySet. </p>

<p>How Baserow lets users generate Django models on the fly: </p>

<p>Django pagination based on the seek method / keyset paging / offset-less pagination: </p>

<p>How can I cast a DateField() + TimeField() to local time in a Django QuerySet? </p>

<p>How not to structure your database-backed web applications: a study of performance bugs in the wild - </p>

<p>In Django ORM you can add <code>order_by('?')</code> to a queryset to randomize results - but be careful because it can slow them significantly #order-by</p>

<p>Great post on optimizing Django ORM Queries: </p>

<p>If you use iterator() to run the query, prefetch_related() calls will be ignored since these two optimizations can't be used together</p>

<p>Pushing the ORM to it's limits: </p>

How to Use Django Bulk Inserts for Greater Efficiency

<p>Excellent article about how ORMs cause leaky abstractions that lead to performance issues and how fixing them is generally simple: </p>

<p>If you need to get only one field from a related model you should use annotate </p>

<p>How to create symmetrical relationships in Django using ManyToMany's "through" </p>

<p>You can pass a queryset to prefetch_related (and select_related): <code>Restaurant.objects.prefetch_related(Prefetch('pizzas__toppings'))</code> #django.db.models.Prefetch</p>

<p>A Few Django ORM Mistakes </p>