Scott Haneda wrote:
Unless you have very good reason to store binary data like an image in
your database, do not. It may work well for a time, but always be
prepared that your system will grow. If it grows a good deal relative
to your hardware, and users, and connections etc, you will always
-Original Message-
From: mugisha moses [mailto:mossp...@gmail.com]
Sent: Thursday, May 28, 2009 12:11 AM
To: Arthur Fuller
Cc: mysql
Subject: Re: Can a MyISAM DB hold /everything/?
what if you had no issues of scaling, which would have less access
time, file system or database?
[JS] I
The times I have heard, this is just a test, hack it together, or
this will never see significant load are more than I care to count.
Worse, the times that those statements ended up being false, and a
rigged and hacked demo code base become production has taught me to
treat all work as
A bit of a confusing set of replies was in the previous thread...
Doing my best to answer the issue at hand, please reference past posts
if my reply is not clear...
On May 28, 2009, at 6:04 AM, PJ wrote:
Could you clarify/expand on this a bit - I am setting up a site
where I
expect to
Most commonly, you would store all information (including descriptions
in teh database. The amount of data you describe is peanuts for MySQL.
Then, you would probably store a path to an image in the database as
well. You could then store the images on disk outside the database, or
even think about
Unless you have very good reason to store binary data like an image in
your database, do not. It may work well for a time, but always be
prepared that your system will grow. If it grows a good deal relative
to your hardware, and users, and connections etc, you will always be
in a race to
I second that emotion (don't store the images in the data file: just store
the paths to said images). Why? Because in the event of an updated image it
is more hassle than it is worth, to drop the old image and replace it with
the new one; if what you store is a simple pointer to an image file,
what if you had no issues of scaling, which would have less access
time, file system or database?
On Thu, May 28, 2009 at 1:54 AM, Arthur Fuller fuller.art...@gmail.com wrote:
I second that emotion (don't store the images in the data file: just store
the paths to said images). Why? Because in
