On 01/11/13 00:35, Mike wrote:
My users will upload text documents ranging from hundreds to thousands of words. At the moment I store the text in a TextField. Is this going to cause a performance problem in the future or would it be better to store the text on the file system and put a file path in the data model? The text does not need to be indexed and I'm using MySQL.
If it doesn't need to be indexed (by which I also assume that you're not searching by its contents), that's actually a pretty small quantity of data to stash in a TEXT field. So it should pose no problem. The only other issue might be if you have cases where you bring back large quantities of these fields and try to display, in which case you're pulling N records time M average-bytes-per-text-record. But usually users don't want to see that sort of volume of data.
I suppose the best way is to profile the app and see if the text retrieval is a bottleneck but I thought someone on this list would already have experience in this.
I'd code under the assumption that it's not an issue, and then profile if it becomes one.
-tkc -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
