First of all I know that is bound to break a lot of other things.
I changed the core so references to tables are PostgreSQL fully qualified
table name (e.g. "family"."person" instead of family_person). So far it had
been doing what I want except I can't run tests because the schemas are not
cre
If we chain a call to filter() after a call to distinct(), the filter is
applied to the query before the distinct. How do I filter the results of a
query *after* applying distinct?
Example.objects.order_by('a','b').distinct('a').filter(b='something)
The where clause in the SQL resulting from
This better illustrates what I mean:
Example.objects.order_by('a','foreignkey__b').distinct('a').filter(foreignkey__b='something')
On Tuesday, June 10, 2014 4:06:50 PM UTC-5, John Rambo wrote:
>
> If we chain a call to filter() after a call to dis
How do I switch to version 1.7 in git when I have the current repository?
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-users+unsubscr...@googlegroups.c
If I try to run test suites in 1.7 with admin in INSTALLED_APPS, I get
this...
File "/django/core/management/commands/migrate.py", line 195, in
model_installed
(opts.auto_created and converter(opts.auto_created._meta.db_table) in
tables))
AttributeError: 'bool' object has no attribute '_m
5 matches
Mail list logo