[JJR512]

PPN, I have a question for you.

It's concerning vBulletin 3, and the features described in this thread: http://www.vbulletin.com/forum/showt...threadid=51821

John mentions that attachment images (.gif,.jpg.,etc) are no longer stored in the database. I'm assuming this means text files, .zips, and whatever other formats are allowed are still stored in the database. My personal opinion of this is that all formats should be stored outside the db. I can see that some formats, especially text files, might typically be so small that it doesn't make a big difference, but it seems like it would be unnecessarily complicated from a programming point of view to have two different attachment handling routines.

I don't know if you know the answer to this, but I'm curious to know if there will be an administrative way of controlling which attachment types get stored where. Some board admins may allow other file types that could be as large as, or larger, than image files, making them also be good candidates for storing outside the database.

But, PPN, what I'd really like to know from you, is when vBulletin 3 comes out, what's going to happen to those of us who have installed your hack? I know I've long ago gotten rid of the field in the attachments table that stored all the file data, and even if I still had a copy somewhere, there's plenty of new attachments since then that were never put into that field. Will you be able to adjust this hack pretty quickly to work with vB 3, so that those of us using your hack won't have to wait that long before we can start using vB 3 without losing attachments? Or can you make something to basically reverse your hack, something that will re-import all attachment files back as filedata into the database?