Re: select_for_update and transactions (bad dev UX in a feature)

2021-11-20 Thread Aymeric Augustin
Hello, > On 18 Nov 2021, at 11:11, Florian Apolloner wrote: > > FWIWI I always recommend disabling ATOMIC_REQUESTS and using transactions as > needed :) Investing engineers' time into evaluating the exact transactional integrity requirements of every view may be appropriate in some contexts.

Re: select_for_update and transactions (bad dev UX in a feature)

2021-11-20 Thread Florian Apolloner
Hi Aymeric, On Saturday, November 20, 2021 at 12:39:17 PM UTC+1 Aymeric Augustin wrote: > I'm not trying to disagree for the sake of disagreement; I'm just trying > to bring some contextual awareness and avoid the "core devs say > ATOMIC_REQUESTS is bad" effect. I hope we can agree on this? >

Question: Regarding Page class

2021-11-20 Thread Gullapalli Saisurya Revanth
Hi, While working with pagination I have observed that after splitting a queryset into pages. Each page that is initially of type queryset is converted to list before returning. Is there any reason why it's converted to list? I see that we can still get a queryset by slicing it which we could

How to get started with contribution

2021-11-20 Thread Asma Butt
Respected Sir/madam, I am Asma Butt, a computer science undergrad,I have just entered my third year at BSCS (UET).I am new to open source contributions but I am well aware of python and currently learning django framework.I would love to contribute to your organization but could you please tell

How to get started with contribution.

2021-11-20 Thread Vinayak Saxena
Respected Sir/Madam, My name is Vinayak Ravi Saxena, a computer science undergraduate, I have just entered my final year at Lovely Professional University. I am a newbie at open source and looking forward to starting my open-source journey with your organization. I am proficient in C++, Python,

Re: select_for_update and transactions (bad dev UX in a feature)

2021-11-20 Thread Carlton Gibson
On Sat, 20 Nov 2021 at 14:21, Florian Apolloner wrote: > I even have a possible fix for that, but it requires us to rewrite > middlewares again :/ > This is the third time this has come up (the middleware rewrite I mean) Rule of Threes. We need a DjangoCon, so we can draft a DEP. :) > -- You