Board Thread:General Discussion/@comment-667748-20130513104011/@comment-667748-20130517111033

My experience is that it all on a single page brings the same problems as having it on different pages, but also adds a lot of code complexity. The final page is a huge clusterfuck: User:Happypal/Sandbox/ArmorDatabase.

Also, it MASSIVELLY burdens the servers: For starters, the entire wiki gets refreshed every time the code gets touched. Second, it requires parsing a single page which is thousands of K big, as opposed to selectivelly parsing only the page(s) of interest.

It is possible, I just don't think it is the best approach.

I just threw together a "same page db". Look at this code: User:Happypal/Paladin Helm. As you can see, intrusion is "minimal". Users can edit it without even realizing it it is part of a database. It isn't quite perfect yet, and there is some "duplication" with the existing fields, but nothing that can't be smoothed out. Proof that it works is here in this code section [[User:Happypal/Sandbox#In-page DB.