Re: The cotent types framework unreasonably limits model name length.

I think a problem with hashing names here is that it would break the whole `apps.get_model(, )` functionality that content types uses, as the model name stored in the db is not the actual name stored in the apps registry (and modifying the registry functionality feels like the wrong approach

Re: The cotent types framework unreasonably limits model name length.

> You should be able to work around this for now with a migration in your own app that uses RunSQL to alter the column for ContentType.model. I tried this approach however the ORM level field validation still kicks as it still expects VARCHAR 100 even if the db column is now a different type.

Re: The cotent types framework unreasonably limits model name length.

> Suffix-hashing long names like Simon suggests may not be backwards-compatible. Could you elaborate on that? Assuming model names > 100 characters never worked wouldn't only suffix-hashing model names > 100 characters be backward compatible? Simon Le mardi 11 août 2020 à 12:05:46 UTC-4,

Re: DjangoProject

Hello Desh, I would love to collaborate with you. My Github username is* remiljw* Thanks. Virus-free. www.avast.com

Re: DjangoProject

We can work in a project with few members as a group work. On Tue, Aug 11, 2020, 22:47 Desh Deepak wrote: > Hello everyone, I want to developing a django project. Who wants to > collaborate to do a project and learn django share your github user id for > github reposetory access. > > Live on

Re: DjangoProject

https://github.com/giftbalogun On Tue, Aug 11, 2020 at 6:03 PM Desh Deepak wrote: > Hello everyone, I want to developing a django project. Who wants to > collaborate to do a project and learn django share your github user id for > github reposetory access. > > Live on Heroku >

Re: DjangoProject

Hi! I think you've found the wrong mailing list for this post. This mailing list is for discussing the development of Django itself, not for support using Django. This means the discussions of bugs and features in Django itself, rather than in your code using it. People on this list are unlikely

DjangoProject

Hello everyone, I want to developing a django project. Who wants to collaborate to do a project and learn django share your github user id for github reposetory access. Live on Heroku http://kidszania.herokuapp.com/ Thanks Desh Deepak +91 7011101001 -- You received this message because you

Re: The cotent types framework unreasonably limits model name length.

AFAIK Postgres, in these cases, simply truncates the name. This means: 1) Generating models with names longer than 63 characters on postgres is fragile. You may find yourself with more than one model trying to use the same table name. 2) Suffix-hashing long names like Simon suggests may not be

Re: The cotent types framework unreasonably limits model name length.

I agree this limitation of `contrib.contenttypes` is a bit unexpected. Not saying we should lift it but it does seem arbitrary even if having such large table names could be considered bad practice. One approach we could take that doesn't involve any migration is to fallback to hashing of the

Re: The cotent types framework unreasonably limits model name length.

*contenttypes* should support all backends, You need to remember about DB-restrictions, e.g. we cannot change `ContentType.model` to a `TextField` because TEXT columns cannot be used in unique constraints on MySQL. See similar discussion

Re: The cotent types framework unreasonably limits model name length.

It does seem unreasonable. I think a migration to TextField would be warranted. You should be able to work around this for now with a migration in your own app that uses RunSQL to alter the column for ContentType.model. On Tue, 11 Aug 2020 at 04:26, Richard Campen wrote: > I guess I have two

Fellow Reports - August 2020

Week ending August 9, 2020. Released Django 2.2.15, 3.0.9, and 3.1. *Triaged:* https://code.djangoproject.com/ticket/31849 - django-admin startproject - Fails to create files after encountering CommandError (wontfix) https://code.djangoproject.com/ticket/31848 - Support namespaced