I've worn myself out on this topic over the past two months, I'm too mentally drained to really read Elliot's explanation (sorry, Elliot)
But, FWIW, there might be a built in way to allow different databases within the new framework, since it was a much-asked for feature. (The ability to have a classified and links database, for example). Either way, there is a way to run multiple databases, and once the new version comes out I'll be working on that aspect (within the license agreement).
As for the MySQL table, it can hold _anything_. It has a text field, as well as a "blob" field, so it can even hold and serve graphics.
Because of the way indexes work, the larger fields don't really slow anything down, _except_ the re-index and initial add -- when all the text has to be scanned, parsed, and put into the indexes.
The size of the database is really limited by diskspace, and your ISP, but the larger it gets, the more important REGULAR BACKUPS!! are!!
http://www.postcards.com
FAQ: http://www.postcards.com/FAQ/LinkSQL/
But, FWIW, there might be a built in way to allow different databases within the new framework, since it was a much-asked for feature. (The ability to have a classified and links database, for example). Either way, there is a way to run multiple databases, and once the new version comes out I'll be working on that aspect (within the license agreement).
As for the MySQL table, it can hold _anything_. It has a text field, as well as a "blob" field, so it can even hold and serve graphics.
Because of the way indexes work, the larger fields don't really slow anything down, _except_ the re-index and initial add -- when all the text has to be scanned, parsed, and put into the indexes.
The size of the database is really limited by diskspace, and your ISP, but the larger it gets, the more important REGULAR BACKUPS!! are!!
http://www.postcards.com
FAQ: http://www.postcards.com/FAQ/LinkSQL/