day, December 03, 2001 6:48 AM
To: Struts Users Mailing List
Subject: Re: When to store files in DB vs. File system
I've seen a lot of implementations do this sort of thing, especially
when archive emails and the like.
I've also heard that people find many OS's start to slow down with
://www.karora.com/DocConn.htm
Gavin Terrill
CTO, Karora Technologies Inc.
http://www.karora.com
-Original Message-
From: Ted Husted [mailto:[EMAIL PROTECTED]]
Sent: Monday, December 03, 2001 6:48 AM
To: Struts Users Mailing List
Subject: Re: When to store files in DB vs. File system
I&#x
I've seen a lot of implementations do this sort of thing, especially
when archive emails and the like.
I've also heard that people find many OS's start to slow down with even
1000 files in a directory, so I believe many such systems use that as an
increment /1/000 - /1/999.
A general piece of go
Hi.
Everyone is going to tell you that you must store it in the database. The
reason are that in different OS's, there is a limit to how many files you
can store in each directory. (windows i think is 1). I was faced with
this same problem under a time constraint, so never took the time to f
4 matches
Mail list logo
