I'm still very vague at the moment of everything I want to include on it,

Stage 1 of any project is to plan what you want. Often decisions you make at the begining can deeply commit you to a particular course of action. Define what is core (must have) and what is to be placed on the wish list. This way you can get a working system up and then add the frills as time, money and experience dictate.

All i know is it will be large and hopefully I want to make it as scalable as possible ( which shouldnt be hard with a flat file db system )

Sorry, this is just plain wrong. Flat files are the worst possible choice for a project that aims to be large and scaleable. Databases basically sprang into existence to fix the deficiencies of flat files in large, scaleable, robust data applications.

I was going to use mysql but I do not yet have enough knowledge of it at the current moment.

For what you want "Don't leave home without it!"

I agree the everything engine +/- Tim Vroom (click here for vroom) may be a good option.

tachyon