"Ian Charnas" <[EMAIL PROTECTED]> writes:
> yeah! Glad to hear it. I know this doesn't exactly answer your
> question, but I would strongly recommend *not* storing the images in
> the database. There is a really cool way to modify your model using
> "magic attributes" so that uploaded files *look* like they are stored
> in the database, but are actually stored on the filesystem. This lets
> you use all the common image editing libraries (like PIL) with fewer
> headaches! Check out Ian Bicking's excellent documentation:
> http://www.sqlobject.org/SQLObject.html#adding-magic-attributes-properties
Things to consider when deciding where to store images:
- database size
- filename uniqueness
- ammount of images
- filesystem type (some are not optimized to scan thousands of images)
- backup (!!!!)
- integration with other systems
--
Jorge Godoy <[EMAIL PROTECTED]>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TurboGears" 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/turbogears?hl=en
-~----------~----~----~----~------~----~------~--~---
