Hi all,
As you may be aware, Django 1.8 migrations have some performance issues,
especially if you have a lot of apps with a lot of migrations. Django 1.9
improved on this somewhat, and AFAICT Django 1.10 solved the problem, so that
the time taken is really mostly the time taken by database ope
FYI.
The news as far as Django users are concerned are mostly improved support for
Oracle 12c (not yet used in Django core, but available for users nonetheless)
and some minor bugfixes.
Have fun,
Shai.
-- Forwarded Message --
Subject: cx_Oracle 5.2
Date: Sunday 21 Ju
Hi all,
This release of cx_Oracle includes fixes the segfaults encountered with
Python3, and includes significant performance improvements for 64-bit platforms
(where long is 64-bits, so, specifically, Windows not included).
Strongly recommended for all Oracle users.
Have fun,
Shai.
-
The question about aggregates still stands -- however, if anybody is wondering
about finding all childless parents, I figured a way:
On Monday 03 August 2009 17:45:18 Shai Berger wrote:
>
> class Team(models.Model):
> name = models.CharField(max_length=100)
>
> class Play
Hi all,
With the new aggregates in django 1.1, I wonder if there's an easy way to
aggregate over reverse relationships. As an example, assume a simplistic
representation of a set of teams:
class Team(models.Model):
name = models.CharField(max_length=100)
class Player(moedls.Model):
5 matches
Mail list logo
