Fellow Report - February 27, 2016

This report concludes the first year of the fellowship program. Thank you to everyone who contributes to allow it to happen. My contract is renewed for the next six months. I hope the ongoing fundraising efforts enable the program to continue throu

Re: Making max_length argument optional

Hi Shai, On Saturday, February 27, 2016 at 4:44:18 PM UTC+1, Shai Berger wrote: > > I think this is why we should be a little more cautious and go for 128 or > 100, > rather than "the current maximum all-backend-compatible value". > Which somewhat speaks for my point, cause we do not know if t

Re: Making max_length argument optional

Hi Florian, Wim and all, On Saturday 27 February 2016 16:56:25 Florian Apolloner wrote: > Hi Wim, > > On Saturday, February 27, 2016 at 2:33:27 PM UTC+1, Wim Feijen wrote: > > Can you please elaborate why the current situation is better? > > I wouldn't say it is better, just equally good/bad ;)

Re: Making max_length argument optional

Hi Wim, On Saturday, February 27, 2016 at 2:33:27 PM UTC+1, Wim Feijen wrote: > > Can you please elaborate why the current situation is better? > I wouldn't say it is better, just equally good/bad ;) > In practice, most people add max_length=255 everytime by hand. I value > your opinion but

Re: 3 level nested prefetch is not working as expected on Django 1.8.x

Hi, Thanks for taking the time to report this and prepare a detailed test case. However, per our support policy[1], Django 1.8 is now at a stage where the only fixes we apply to it are security fixes and bug-fixes for data-loss issues. As far as I understand from your description, this does no

Re: Making max_length argument optional

Hi Florian, Can you please elaborate why the current situation is better? In practice, most people add max_length=255 everytime by hand. I value your opinion but I fail to understand your reasoning. Could you please explain further (if you have time)? Wim On Saturday, 27 February 2016 14:

Re: Making max_length argument optional

-1 on adding an arbitrary default like 100/128… If people choose a CharField the should set max_length manually. In that sense I am for option 3. Cheers, Florian On Saturday, February 27, 2016 at 1:55:23 PM UTC+1, Wim Feijen wrote: > > Hi guys, > > I'd like to reach consensus about > https://c

Re: Making max_length argument optional

Hi guys, I'd like to reach consensus about https://code.djangoproject.com/ticket/14094 In the discussion, I saw three options: 1. Adding a default max_length = None, which may in practice differ per database backend. 2. Adding a default max_length of a value which can be used across databases