#18416: Query fails when SimpleLazyObject evaluates to None -------------------------------------+------------------------------------- Reporter: bouke | Owner: nobody Type: Bug | Status: closed Component: Database layer | Version: 1.4 (models, ORM) | Severity: Normal | Resolution: wontfix Keywords: | Triage Stage: | Unreviewed Has patch: 0 | Needs documentation: 0 Needs tests: 0 | Patch needs improvement: 0 Easy pickings: 0 | UI/UX: 0 -------------------------------------+-------------------------------------
Comment (by gabn88): Also have this issue now. Now with request.user, but with another object (some model instance) I wanted to be evaluated lazyly. I'm curious how you fixed it? Completely new LazyObject Class, or is there some quick hack? I guess I will do a quick test for None before I create the lazyobject. I guess it takes another database call, but I don't know how to do it otherwise. -- Ticket URL: <https://code.djangoproject.com/ticket/18416#comment:6> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because you are subscribed to the Google Groups "Django updates" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-updates+unsubscr...@googlegroups.com. To post to this group, send email to django-updates@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/063.157da9eb7737c38cd39d41820f412e11%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.