I'm used to using aggregate types in postgres as a convenience. I
whipped up the beginings something analogous to that for django. It
allows definition of "aggregate fields" using a marker base class; it
defines a mixin for Model-derived classes that unpacks "aggregates" and
adds them as individua
Hi Shaun,
On Sat, 2006-05-20 at 10:44 -0700, shaunc wrote:
> Is this the right place to ask about what looks to be a bug? If not,
> sorry
>
> If so, the following code will cause generation of SQL that is missing
> constraints:
[... informative example snipped ...]
> But the bottom line is
Ok, perhaps slightly more pythonic would be:
for refto, refs in references.iteritems():
try:
pending_references[ refto ].extend( refs )
except KeyError:
pending_references[ refto ] = copy.copy( refs )
- Shaun
X-Google-Language: EN
Ok
django.core.management:108:
-
pending_references.update(references)
-
needs to be replaced by something like:
-
doh.. process_view is what I am after..sorry for the noise
On 20/05/2006, at 11:37 AM, Ian Holsman wrote:
>
> I'm just thinking out loud here, but I was wondering what the others
> developers thought of having a event/hook
> which would capture the URL request just after it has been resolved.
> (
Is this the right place to ask about what looks to be a bug? If not,
sorry
If so, the following code will cause generation of SQL that is missing
constraints:
---
# in project 'test'
from django.db.models import (
