Sir,
I am in the situation to storing student and staff images. every year 2000 new
photos has to be added in our application.
Can i have your suggestion, which is the best one, storing as a blob Or using
NFS?
It will be great help to me, because such experts are sharing your own
experience on this binary storage issue.
Thank you.
VIKRAM A
________________________________
From: Johan De Meersman <vegiv...@tuxera.be>
To: Martijn Tonies <m.ton...@upscene.com>
Cc: mysql@lists.mysql.com
Sent: Fri, 12 February, 2010 1:09:32 PM
Subject: Re: how things get messed up
On Fri, Feb 12, 2010 at 8:27 AM, Martijn Tonies <m.ton...@upscene.com>wrote:
> Sounds logical, what's also nice to see, is that even though people here
> tend to say "don't put binaries in the database", apparently Facebook
> thought it would be nice to do so (for all sorts of reasons) and even took
> the time to write their own blob storage mechanism ;-)
The whole point is that they *aren't*' putting blobs in their database -
that has way too much overhead. They're using a custom service that does
nothing but "read from byte X to byte Y". No concepts of tablespaces,
integrity, indices, whatever.
The only thing they store in their database, is the start- and end-byte of
each image.
I doubt they even took it as far as to write a plugin engine - that would
again bring too much overhead.
--
Bier met grenadyn
Is als mosterd by den wyn
Sy die't drinkt, is eene kwezel
Hy die't drinkt, is ras een ezel
Your Mail works best with the New Yahoo Optimized IE8. Get it NOW!
http://downloads.yahoo.com/in/internetexplorer/
