That seems all right to me.
--
Aymeric.
> On 13 Nov 2018, at 16:56, joh...@alumni.upenn.edu wrote:
>
> If the other fields are also 191, i see no reason not to make the change. It
> should be a non-breaking change. And Yes i am that colleague...
>
> On Tuesday, November 13, 2018 at
Hi Adam,
All of your suggestions are perfectly valid things to do (and are in fact
things I've done in the past). This particular project uses data migrations
fairly heavily, and the developers haven't been particularly good about
making sure they run cleanly on fresh databases. We are using
If the other fields are also 191, i see no reason not to make the change.
It should be a non-breaking change. And Yes i am that colleague...
On Tuesday, November 13, 2018 at 4:52:24 PM UTC+1, Tim Allen wrote:
>
> Greetings,
>
> Over the past few releases, several CharFields in
Greetings,
Over the past few releases, several CharFields in django.contrib.auth have
been increased to a max_length of 191: username, first_name, and last_name
immediately
come to mind.
See:
https://groups.google.com/forum/#!msg/django-developers/h98-oEi7z7g/xzjtFMf1BwAJ
I've issued a PR
This mailing list is for the development of Django itself, not for support
using Django. Please use the django-users mailing list for that, or IRC
#django on freenode, or a site like Stack Overflow.
On Tue, 13 Nov 2018 at 08:06, Dipankar wrote:
> Are you planning for open source or your
Are you planning for open source or your personal project?
On Tue, Nov 13, 2018 at 1:10 AM sakkhar saha
wrote:
> Dear All,
> I am Sakkhar form Bangladesh. Now I have a project idea. And i am a single
> man. My Project is Courier Management in Djnago. Please help for the idea.
> How i start my
Hi Mani,
No response can mean either the readers here do not have the same problem
and have no comment, or your implementation does not require much
discussion. In any case, you could continue with the process by proposing a
formal patch, and getting someone to review it once it meets the
