#23676: FileField documentation is confusing about database column
representation
-------------------------------+--------------------
Reporter: jdufresne | Owner: nobody
Type: Uncategorized | Status: new
Component: Documentation | Version: master
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------
The documentation for the model field `FileField` contains the following
line:
> By default, FileField instances are created as varchar(100) columns in
your database.
Personally I find the intent of this sentence confusing. The phrase "by
default", leads me to believe this is something I can modify. Yet, I find
no documentation on how to modify this. I was looking for a way to modify
the `FileField` to be represented as a FK to a custom `FileMetadata`
model. This gave me hope that it was possible. Upon looking for more
documentation and looking at the source, I did not find any clear guidance
on how to approach this.
It seems this should be more of a direct statement by dropping "by
default":
> FileField instances are created as varchar(100) columns in your
database.
--
Ticket URL: <https://code.djangoproject.com/ticket/23676>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/052.65ef8f7df010a5e527a12b7a8d3a11c4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
