Re: Re2: Is it a good idea to store images in a RDBMS?

Consider, that if you store them in database, you will need to extract them into temporary files each time you neet to generate page containing them.

Not necessarily. One could write a CGI / handler that fetches a picture directly from the database, which to a browser, would look no different than a request for a file. This sort of thing was recently discussed here.

   MeowChow                                   
               s aamecha.s a..a\u$&owag.print

Comment on Re: Re2: Is it a good idea to store images in a RDBMS?

Replies are listed 'Best First'.
Re3: Is it a good idea to store images in a RDBMS? by pmas (Hermit) on Jul 21, 2001 at 22:32 UTC
++ for you MeowChow! I did not know trick from your link! Now I recall: It is because every item is loaded from HTTP server to browser separately, by separate request, and only on client side rendered together to make a page. So you can create CGI script which will look like one .gif file for browser. I read about it, but knowledge was not digested. Now it is! So much more to learn! pmas To make errors is human. But to make million errors per second, you need a computer.	[reply]

Replies are listed 'Best First'.

Re3: Is it a good idea to store images in a RDBMS?
by pmas (Hermit) on Jul 21, 2001 at 22:32 UTC

MeowChow

So much more to learn!

pmas

To make errors is human. But to make million errors per second, you need a computer.

[reply]