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 databas
Django documentation clearly disapproves of storing static content in
a database. 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.
--~--~-~--~
2 matches
Mail list logo
