There were dark times when we had like 200 000 images in the database, because the initial developers thought it's the easiest way to control access to them for photo sharing and ordering website. So from that experience I can tell you that it would be slow as hell (it's kind of obvious but still). For example Apache on my laptop can serve 1000+ static files per second and only like 15-20 request/sec for php. My point is if you're going to use this logic for production it will totally kill your performance.
If I were in your place I'd go with the capistrano task thing Just my 2 cents On Tue, Sep 30, 2008 at 3:50 PM, Sean Cribbs <[EMAIL PROTECTED]> wrote: > Errol, > > If you add the appropriate database field(s) and tweak the model, you should > get it to work. I have no idea how one would get the image data back out, > however, since I've never done it. > > Sean > > Errol Siegel wrote: >> >> I know attachment_fu supports this, but I'm not sure if that means >> page_attachments can work with it. >> >> I wanted to see if anybody knows the answer to this before I spend the >> time on trial-and-error. >> >> Thanks, >> Errol >> > > _______________________________________________ > Radiant mailing list > Post: Radiant@radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > _______________________________________________ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant