On Tue, 2009-03-24 at 08:56 -0700, tgorham3 wrote: > Django documentation clearly disapproves of storing static content in > a database.
Well, no, but it acknowledges that a filesystem is usually a better solution for that type of operation, as it's optimised for storing large files (SQL databases are not). > Google App Engine treats blobs in the db as the norm. > > Does Big Table change the rules or is it still preferable to store > static content in the file system and let a server do the heavy > lifting. Big Table is entirely different from a relational database, on so many levels. If you're using Google App Engine, you're running in a very different environment anyway (since Google gives a type of server and it's not something you're configuring yourself). The problem with your question is that almost any answer will be correct for some particular set of circumstances. If you have a particular problem in mind that you're trying to solve and one approach or the other isn't working for you for some reason, try an alternate approach. If you're wondering about the performance characteristics of GAE, ask on their mailing list(s), since the experts over there will know about things. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
