Re: Sealing or locking QuerySets -- a suggestion to prevent surprise N+1 queries.

I'm very interested in this feature and would love to assist in making it happen. On Thu, Jan 4, 2018 at 12:34 AM, charettes wrote: > Hey everyone, > > I also believe this is a feature that should be in core > judging by the number of times I had to enable query logging >

Re: future of QuerySet.extra()?

Would the expressions API be able to define fields that are aggregations of complex foreign relationships? I keep using it when I need fields that are the result of weird aggregations over multiple JOINs with some unusual stuff like CASE fields and subqueries. On Fri, Jul 31, 2015 at 2:58 PM, Tim

Consider reopening ticket #11385

Hi everyone, I wanted to bring up a request: Ticket #11385 dealt with Django's DateTimeField being unable to handle ISO 8601 date formats. At the time it seemed reasonable to not support this feature given, however, given the proliferation of web service APIs that return dates using this format,

Re: When to use single quotes and double quotes

I don't know where I got this from, but I consider it to be the best convention for choosing quote types: Use double quotes for strings meant for human consumption, use single quotes for everything else. Text, trans strings, model verbose_names: double quotes Dict keys, HTML tags, flags, and

Re: Add strutctured settings module to django 1.7?

Honestly, I find the idea of *not* using a settings file to be inconvenient, and the notion of using environment variables for doing anything aside from pointing to a settings file to be pretty disgusting. Here are my thoughts, in no particular order: - Pretty much everyone out there uses some

Re: Admin for proxy model for custom User

gus Turner > angusisf...@gmail.com > > > On Wed, May 29, 2013 at 10:33 AM, Andres Osinski <andres.osin...@gmail.com> > wrote: >> >> Hi everyone, I've created a custom User model and reated a proxy for >> it, like this: >> >> class User(Abstrac

Admin for proxy model for custom User

Hi everyone, I've created a custom User model and reated a proxy for it, like this: class User(AbstractUser): USER_KINDS = ( ('d', 'doctor'), ('p', 'patient') ) kind = models.CharField(max_length=2, choices=USER_KINDS) class DoctorManager(BaseUserManager): def

Re: Perception of attitude in tickets

I really don't know how you think you'll be getting a different response in other frameworks, because the core developers' attitude on this is correct. There are over 2 tickets in the bug tracker for a project used by tens of thousands of people. Code has to pass style guidelines, regression