Anatol Mayr / HEXAGON wrote:
> Hi!
>
> We've been playing around with midgard and have seen that the pictures
> in the example sites are stored locally.
> Is there an easy way to store pictures in the MYSQL-Database, so
> that we can keep the whole site in the database?
>From a pure systems point of view, I fail to see why anyone would want
to. If the picture is accessed from the file system, it is served as an
http request, but we are all using keep-alive, aren't we, so there should
be minimal overhead here.
If the file is stored in the database as a large object, then the entire
file must be packaged into some shared memory location and transferred to
whatever process is looking for it. Now, getting it out of the database
is still a filesystem access, with the additional overhead that the data
base puts on it.
I don't know the internals of mySQL, but I have not seen a data base that
does both a clean and a fast job of serving large objects. (Maybe
Oracle, never tried.) It has always been my contention that this is why
these things are called BLOBs instead of just plain BLO (Binary Large
Object), since who wants to deal with a bad BLO job?
SGI created a specialized file system to do video service precisely
because of these types of problems, and note that their solution is NOT a
database, but a filesystem.
cat
>
>
> Bye,
> Anatol
>
> --
> This is The Midgard Project's mailing list. For more information,
> please visit the project's web site at http://www.midgard-project.org
>
> To unsubscribe the list, send an empty email message to address
> [EMAIL PROTECTED]
--
This is The Midgard Project's mailing list. For more information,
please visit the project's web site at http://www.midgard-project.org
To unsubscribe the list, send an empty email message to address
[EMAIL PROTECTED]
