At 04:36 3/10/00 -0400, you wrote:
>Looking through the docs, one of the current restrictions kind of jumped out
>at me: "The size of Binary data is limited to about 32 KB (because UTF is
>used) " Does this mean I can't have a LONGVARBINARY (or LONGVARCHAR) more
>than 32k? If this is the case, we can pretty much stop considering it an
>option, so I'm hoping it's not.
Well the best way (and the way I did it ;]) is to actually have the binary
chunks on filesystem and all important envelope/headers/details in DB. This
allows most searches/retrieval to be efficient but still relies on
filesystem for large chunks. It is a lot faster but it also assumes that
database is on same system as server. It can be a bitch when you have a
central db but distributed servers who each write messages to their own
filesystem but I have yet to think of a safe way around it.
Cheers,
Pete
*------------------------------------------------------*
| "Nearly all men can stand adversity, but if you want |
| to test a man's character, give him power." |
| -Abraham Lincoln |
*------------------------------------------------------*
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives: <http://www.mail-archive.com/james%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
