The reasoning behind having a MySQL backend is for extremely large or active systems only.
The base UBB system is designed around small to medium sized systems where the flat file system do not exceed 20,000 in their respective groupings (i.e. members <= 20,000 files : Topics <= 20,000 files) CC has done an amazing job at coding UBB for this market segment and I am sure has alot of surprises for the future.
The 20,000 is seemingly a magic number as Linux has problems with directories that exceed this number of files. It will still work but try listing them. You can get around this by recompiling the Kernal if really necessary.
What you can do if you are really still wanting this is make it a hybrid system. Database the users and topics but leave the flat file system in tact for the rest.
Is it worth the effort? Honestly nope. Why did we do it? As an already established system running with v5.47 it was my familiarity with UBB, users familiarity with UBB in terms of look and feel. Plus I like to be different
Also realize if you ever did database your UBB you will never be able to upgrade to a newer version. Anything going forward will have to be custom coded.
You really should take a look at UBBThreads if your set on a database system. The amount of support is equal to UBBDev over at ThreadsDev. I think you will be pleasently surprised.
And as a large UBB system CC will tell you flat out that Hostboard does not count :rolleyes:
BTW, you should really consider upgrading. There have been tremendous strides since the version you are running in performance, features, etc
...Steven
Hostboard.com Running UBB v6.1.0.4
Doing what
NO other UBB in the world is doing.
The
first &
only production UBB powered by MySQL.
