alt.apache.configuration Google Group

Re: how to secure documents in server

2008-07-19T15:24:31Z

Shows a lot of bis there and many usupported assertions. Some of which
ARE wrong.

Re: how to secure documents in server

2008-07-19T15:21:22Z

Good point.

Re: how to secure documents in server

2008-07-19T13:16:05Z

Which is not entirely accurate...

Re: how to secure documents in server

2008-07-19T09:45:29Z

In fact, a filesystem is a ~DBMS that handles just one type of data
(files). But the amount of metadata that a filesystem (easily) keeps/
provides about its data (the files) is limited, while there's no limit
to the amount of metadata that can be (easily) saved/retrieved in a
DBMS. Both are (most likely) equally well optimized to do their jobs

Re: how to secure documents in server

2008-07-19T09:04:42Z

.oO(The Natural Philosopher)
Some more pros and cons:
[link]
Micha

Re: how to secure documents in server

2008-07-19T07:36:15Z

Actually I guess I ought to qualify my timings comment. I have no proof that
it is the database that was slowing things down per-se. To serve the images
required invoking a load of script, which wasn't going to help and of course
the MySQL installation was on a shared server, so no opportunity to optimise

Re: how to secure documents in server

2008-07-19T07:32:57Z

Also, and this is the bit I really like, when you delete the record the file
automatically goes with it.

Re: how to secure documents in server

2008-07-19T05:38:45Z

Yes. Exactly. The key is to not get religious about it ..."the RIGHT way
is to.."
Advantages of the database...
- one point backup of all data
- definitely not directly accessible via HTML
- has much better indexing and searching than a flat file system in a
directory.
- possibly simpler integration with other bits of data assciated with te

Re: how to secure documents in server

2008-07-19T00:35:47Z

Not at all, if the database is properly configured.

Re: how to secure documents in server

2008-07-19T00:34:58Z

Yes, but with that many files in a directory, even Linux slows down
quite a bit. It isn't made to handle that many different files.
But for a good database, you're just starting.

Re: how to secure documents in server

2008-07-19T00:33:31Z

Over 20 years of experience doing it, starting with DB2 on mainframes.
But don't count MS Access in there. Use a real database. MySQL
qualifies. And it has to be configured properly.
BTW - benchmarks tell exactly one thing - how a database runs UNDER
THOSE CONDITIONS. Change the conditions and benchmarks aren't valid any

Re: how to secure documents in server

2008-07-18T20:39:48Z

I have always found it slightly slower to get the equivalent file from the
database rather than from the file system. But as I say, it doesn't bother
me. If the application is generally better with the files in a database,
that's where they go. If the application is easier with them on disk, then I

Re: how to secure documents in server

2008-07-18T20:25:43Z

I would be interested to see some articles or benchmarks about this
issue. Got any ? From my experience I've actually always encountered
the opposite (MySQL and MS Access) whose performance dramatically
decreases with larger BLOBS. I'm working with many GB's of pictures
for whom I store nothing in tables (ID of the record = name of the

Re: how to secure documents in server

2008-07-18T20:23:29Z

yes, but that is pretty insignificant with e,g. the disk speed issues
and download bandwidth, which are the same in both cases.

Re: how to secure documents in server

2008-07-18T20:17:09Z

I think the point is that retrieving such a large data chunk from a db
might momentarily impact the performance of forthcoming db operations,
think about what happens to the sql database caches.
--Jorge.