Re: images in databases
Re: images in databases
- Subject: Re: images in databases
- From: Mark Morris <email@hidden>
- Date: Sat, 26 Feb 2005 15:39:09 -0600
I have in the past used each approach. (Well, I've used the db
approach once, filesystem every other time.)
The primary advantage of using the database has been mentioned already
in this thread: You get to use EOF, with all that that gives you.
If the image is really an attribute of the entity (such as an image of
a catalog item), and especially (as in my one case) if an end user is
responsible for uploading and maintaining the images, it certainly
simplifies the application to use the db (and gives you things for
free, like easy rollback if you'd like to let them review before
commit, etc.). Yes, you can store the path to the image instead (and
I've done that, too), but you have to admit there's some extra code
there. Plus, now your data's more distributed, which you'll have to
remember for backups, restores, migrations, etc.
All that said, it'd have to be a very specific situation before I'd
consider storing images in the db, but I don't think it's evil in
*every* case. :-)
Regards,
Mark
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden