Re: Clearing prefetch related on add(), change(), remove()

To be clear, I think the way to force the refresh of an orm object is to use the `refresh_from_db` method. Is that functionally equivalent? -Ben On Tuesday, June 7, 2016 at 6:12:30 AM UTC-7, Marc Tamlyn wrote: > > I may be "too close" to knowing the implementation of this feature to be > able

Re: Clearing prefetch related on add(), change(), remove()

I am for the clearing of the cache--that behavior seems weird. If you didn't want the cache to clear you would probably be using a different orm object to do your query. Just to be clear, after clearing the cache, any future requests against that data will be lazily evaluated right? -Ben On

Scaling Django for Multiple Teams

Hey, I have two issues I'm looking at solving at work, and I'm looking for a couple suggestions as to how other people have solved this. The two things are: * scale out their django installation to allow for smaller releases (I'm thinking microservices, but it could also be internal django

Re: Collectstatic and determine which files need to be updated by comparing their checksum

This makes a lot of sense to me. On Tuesday, April 12, 2016 at 9:07:51 AM UTC-7, Daniel Blasco wrote: > > Hi, > > I posted this in django-users but I think that it goes better here. > > > I'm using django-storages to upload my static files to Amazon S3 and I'm > serving my application from

Re: Collectstatic and determine which files need to be updated by comparing their checksum

On Tuesday, April 12, 2016 at 9:07:51 AM UTC-7, Daniel Blasco wrote: > > Hi, > > I posted this in django-users but I think that it goes better here. > > > I'm using django-storages to upload my static files to Amazon S3 and I'm > serving my application from Heroku. > > In my local development,

Re: Revisiting lazy middleware initialization

I'm not too familiar with the code you're referencing, but I'm personally really annoyed by lazy loading. It has a tendency to make selenium tests timeout inconsistently in CI, as well as give the impression to my bosses that the app is slow rather than just the first load which is usually

Re: [ GSoC2016 ] Integration of django and angular2

In terms of a front end application using django views you can totall implement angular, and do whatever you want. If you're proposing that the backend be rewritten in angular, I think that is probably unnecessary overhead for what the admin is supposed to do, and will make customizing it

Re: Composite Primary Keys

Sounds cool, I think we would totally use that. On Wednesday, February 17, 2016 at 1:55:15 AM UTC-8, Roger Gammans wrote: > > Hi, > > > We've got some patches that we are using in production, against > 1.8 . Out long term aim would be to get them ready for a PR , but I they > are missing all

Re: thinking about the admin's scope and its description in the docs

While I think it's true that a process centric workflow (wizards, or hubs anyone?) would be incredibly useful, that does not take away from the fact that the model centric admins are also incredibly useful, and time saving. It's so easy to add search, sorting, bulk actions, etc to an

Re: PostGres 9.5 Upsert

After thinking about it a bit, I think the only function that would really benefit from this would be the update_or_create. If you're doing get_or_create you still need a second query to get the actual row. On Friday, January 8, 2016 at 4:13:26 PM UTC-8, bliy...@rentlytics.com wrote: > > Hey

PostGres 9.5 Upsert

Hey Guys, Postgres 9.5 has added the functionality for UPSERT aka update or insert. Any interest in aligning UPSERT on the db layer with the get_or_create or update_or_create functionality in django? Sounds like my company would be interested in doing the work if the PR will get the

Re: MOSS Award to Django

Hey, Channels sounds a lot like celery (or celery sounds like part of channels). Is that a fair read? Looking for tighter REST integration either way. Thanks, -Ben On Friday, December 11, 2015 at 10:19:00 AM UTC-8, Andrew Godwin wrote: > > Hi everyone, > > For those who haven't seen,

Re: __ne, #5763

I have to say, the lack of __ne is very inconsistent for people new to django, but veterans at sql. It's just one more frustration point when you're trying to learn a new ORM. -Ben On Friday, November 20, 2015 at 11:37:02 AM UTC-8, Carsten Fuchs wrote: > > Hi all, > > sorry if this is a

Re: Should contrib.auth include support for 2fa out of the box?

+1 This sounds like a great feature, depending on the implementation. On Monday, October 26, 2015 at 10:22:46 AM UTC-7, Tim Graham wrote: > > On Trac [1], Alex says, "Django did a tremendous service to its users by > making strong password hashing be the default. The world is pushing >

Re: [Feature] On CommandError, sys.exit(1)

Hm, let me check it out and get back to you. We had some migrations that exited in failure, but with a non-0 exit status during our release. I'll see if I can reproduce this this week. -Ben On Monday, October 26, 2015 at 11:21:17 AM UTC-7, Tim Graham wrote: > > The place you linked to is

Re: Ticket 2273: django.contrib.auth.models.User: username is case-sensitive

> -1 on changing the check of usernames at login to case-insensitive > +1 with preventing the creation of new usernames Ditto On Thursday, October 22, 2015 at 9:33:02 AM UTC-7, mtnpaul wrote: > > Yeah, I was referring to the post by Daniel at the start of the thread, > not Reid's comment. > > I

Re: [Feature] On CommandError, sys.exit(1)

Is it ok if I do a PR on this? This seems like it would be really useful for automation. -Ben On Thursday, October 22, 2015 at 2:20:18 AM UTC-7, Ben Liyanage wrote: > > Hey, > > What do you guys think about this feature request? > > > On CommandError, sys.exit(1) > > It would be pretty easy to