Tweet
Hey Guys,
I just tried to upload a 20M pdf to a thread and, after sorting out the memory_limit, post_max_size and upload_max_filesize params in php.ini, I'm getting a DB error with a 20MB insert statement (aka really big email).
So I checked vb_attachment and it looks like 'filedata' is mediumblob which, from my searching on the net tells me that the max size of the blob is 2^24 (or about 16M).
Would there be a performance hit from changing that to a longblob (other than the extra one byte used for each attachment)? If not, I'd like to recommend that vB make that column a longblob by default. I don't see why we'd want to introduce additional constraints when we don't have to.
I mean hell, we've got php limiting post, upload and memory while vB is limiting the file size before the insert. I think that it should be safe to allow the DB to do the large file sizes by default.
Thoughts?
Cheers,
Dave.
I just tried to upload a 20M pdf to a thread and, after sorting out the memory_limit, post_max_size and upload_max_filesize params in php.ini, I'm getting a DB error with a 20MB insert statement (aka really big email).
So I checked vb_attachment and it looks like 'filedata' is mediumblob which, from my searching on the net tells me that the max size of the blob is 2^24 (or about 16M).
Would there be a performance hit from changing that to a longblob (other than the extra one byte used for each attachment)? If not, I'd like to recommend that vB make that column a longblob by default. I don't see why we'd want to introduce additional constraints when we don't have to.
I mean hell, we've got php limiting post, upload and memory while vB is limiting the file size before the insert. I think that it should be safe to allow the DB to do the large file sizes by default.
Thoughts?
Cheers,
Dave.
Comment