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
for ContentType.model.
>
> On Tue, 11 Aug 2020 at 04:26, Richard Campen > wrote:
>
>> I guess I have two answers to that:
>>
>> 1) Specifically, in this instance I am scripting the creation of a whole
>> bunch of Django models as there are too many to do manually
; On Tue, Aug 11, 2020 at 6:06 AM Richard Campen > wrote:
>
>> Hello
>>
>> I have hit what I feel is an arbitrary limit on the length of a django
>> model class name. I am using the PostgreSQL backend, which smartly
>> truncates table names above a certain siz
Hello
I have hit what I feel is an arbitrary limit on the length of a django
model class name. I am using the PostgreSQL backend, which smartly
truncates table names above a certain size (normally 63 characters) which
means in theory a table name can be of indeterminate length, as PostgreSQL
Hello
I am currently looking at implementing a custom file hashing function when
using the ManifestFilesMixin class to provide white list based file hashing
of static files.
In the process I have found what seems to be an unintended result of
returning `None` from a custom `file_hash()`
