storing large amounts of text in the DB
Mike
iñigo medina
El 11/01/2013 07:36, "Mike" <mike...@gmail.com> escribió:
>
> 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.
That depends pretty much on the operations you perform over such field. Fetch? Search? Concurrence updates?
Iñigo
>
> --
> You received this message because you are subscribed to the Google Groups "Django users" group.
> To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/5CA4p7wHPmoJ.
> To post to this group, send email to django...@googlegroups.com.
> To unsubscribe from this group, send email to django-users...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Mike
On Friday, January 11, 2013 9:30:39 AM UTC+1, iñigo medina wrote:
El 11/01/2013 07:36, "Mike" <mike...@gmail.com> escribió:
>
> 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.That depends pretty much on the operations you perform over such field. Fetch? Search? Concurrence updates?
Iñigo
Sreenivas Reddy T
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. 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.
Tim Chase
> 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.
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.
profile if it becomes one.
-tkc
Mike
On Friday, January 11, 2013 7:47:18 AM UTC+1, Srinivas Reddy T wrote:
On Fri, Jan 11, 2013 at 12:05 PM, Mike <mike...@gmail.com> wrote:
My users will upload text documents ranging from hundreds to thousands of words.What kind of documents? pdf? word docs? excel?
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?
If you are uploading to a folder and storing the path in db, then when somebody moves the folder, then you need to update the all the corresponding paths in the database.When somebody deletes the folder, then everything will be gone.You need to take care of handling duplicate names too.