I tend to disagree - at my place of employment, a newspaper, we have
hundreds of gigabytes of BLOB data (ad and page layouts & digital
artwork) stored in SQL databases. Granted we are using Sybase for
that and not MySQL but there are a lot of advantages to it - access
control, change control and tracking, easy insertion and deletion,
and access from any client right through the database driver so you
can repurpose content more easily.
I have stored smaller amounts of BLOB data in MySQL for side projects
in the past, without trouble.
Do understand though that storing BLOB data in the db will impact
your table optimization and repair times as well as backup/recover
times.
You might also want to plan ahead and devise a scheme to spread the
data among several tables, to allow optimization of just one table a
day (for example) and even to allow you to split storage across
multiple devices should your database get too large.
Dan
At 3:09 PM +0200 10/13/05, Jigal van Hemert wrote:
Kane Wilson wrote:
But when i try to store little but huge gif files it wont store .
First of all, use the method described at
http://www.php.net/manual/en/features.file-upload.php for a safe way
to handle file uploads. It could be that you run into a server limit
which will show up if you use that method.
I do think that you exceeded the max_allowed_packet size for MySQL
queries which has a default value of 1048576 (=1MB). You can
increase this number (must be done in both client and server!!), but
it is usually best to store huge files in a file system and not in a
database.
Kind regards, Jigal.
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:
http://lists.mysql.com/[EMAIL PROTECTED]
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
