I just pushed the patch to master. I didn't do anything to the API in the latest pull. No only=True or .only(), and earliest() and latest() still exist. I didn't feel like bikeshedding this issue any more.
I am happy that we now have some way to get single object from a queryset without using try-except. Thanks to all who contributed! - Anssi On 17 touko, 02:29, Selwin Ong <[email protected]> wrote: > Hi Shai, > > We can add args and kwargs later when it's actually needed, it's not needed > right now and it' cleaner, I think. > > As for "only=True", these methods are meant to replace "latest()". If someone > ones to ensure that the queryset returns only one object, I dont think > "Queryset.get()" is going anywhere soon so they should use that. Besides, > "first()" and "last()" don't really make sense if you expect a queryset to > only return a single object - ordering doesn't matter. > > That's just what I think though. > > Best, > Selwin -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
