On Tue, Mar 13, 2001 at 04:18:41PM +0100, Alessandro de Manzano wrote:
> I'm planning to deploy MySQL for a project of my company but I've some
> concern about real size limit of BLOBs.
>
> I read on Paul DuBois' excellent book that longblob are 2^32-1 wide,
> but actually the communication _protocol_ between clients and server
> limits to 24Mb the dimension of a single record.
>
> It is still true ? or, maybe, have been "fixed" ?
>
I guess it still is in 3.23.33. You might want to look at the TODO for 4.x?
> What workarounds could I use ?
>
Well, if you *really* need to store blobs of over 24M, I would try to use
the string append (or +) and SUBSTR functions to access the blob in parts.
Never tried it though. If the data can change you need to use some locking
mechanism while you fetch or update the BLOB in parts.
This and any other solution that stores the data in MySQL would be awkward
to use until the protocol limit is changed. In any case, it requires multiple
queries. You might want to hide the implementation in some separate module of
your code, so you don't need to make changes everywhere when you decide to
change the implementation (e.g. when the protocol limit is lifted).
> Besides bypassing this problem (not using MySQL to save such BLOBs)
> there are other solutions ?
>
Storage on a shared file system would be preferable in most cases, like
someone else mentioned in his reply.
Regards,
Fred.
--
Fred van Engen XO Communications B.V.
email: [EMAIL PROTECTED] Televisieweg 2
tel: +31 36 5462400 1322 AC Almere
fax: +31 36 5462424 The Netherlands
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
