Changes between Initial Version and Version 3 of Ticket #25615


Ignore:
Timestamp:
Oct 27, 2015, 8:21:13 AM (9 years ago)
Author:
Tim Graham
Comment:

Please provide a minimal sample project that works on 1.6 and fails on 1.8. The simpler you can make the sample project, the easier it will be to determine if it's a bug in your application or in Django. Thanks!

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #25615

    • Property Component Uncategorized → Database layer (models, ORM)
    • Property Type Uncategorized → Bug
    • Property Summary multidm Relation fields do not support nested lookups → multidb Relation fields do not support nested lookups
    • Property Resolution → needsinfo
    • Property Status new → closed

  • Ticket #25615 – Description

    initial v3  
    1 He all,
    2 
    3 Does anyone know why i can't do any relation lookups on any database other then the default database in 1.8.5 this worked fine in 1.6.1
    4 it keeps trowing me: Relation fields do not support nested lookups
     1Does anyone know why i can't do any relation lookups on any database other then the default database in 1.8.5 this worked fine in 1.6.1. It keeps telling me: `Relation fields do not support nested lookups`.
    52
    63for example on
    7 adds = ProfielenFlirts.objects.filter(voor__user__profielenuserprofile__fictief=True).filter(Q(antwoord='') | Q(antwoord__isnull=True)).count()
     4`adds = ProfielenFlirts.objects.filter(voor__user__profielenuserprofile__fictief=True).filter(Q(antwoord='') | Q(antwoord__isnull=True)).count()`
    85
    96ProfielenFlirts is a non default database, the relation lookup is in the same database do.
    … …  
    118
    129my router
     10{{{
    1311class DatingRouter(object):
    1412    def db_for_read(self, model, **hints):
    … …  
    3432        else: # but all other models/databases are fine
    3533            return True
    36 
    37 any help would be appriciated
     34}}}
Back to Top