Just from a point of storage, the wp_posts table has a bigint(20)
http://codex.ww.wp.xz.cn/images/9/9e/WP3.0-ERD.png
The max for an unsigned bigint(20) is 18,446,744,073,709,551,615
So even with a lot of post revisions, attachments, and so forth, you should be OK. However there are other considerations.
Thank you. It is the ‘other’ I need to consider.
I have an existing site but it has to move and to move on. It is all custom built code, and I have little desire to re-invent the wheel a second time.
Is there an obvious wordpress site with similar or substantially more postings?
Thank you. Point gladly taken.
WordPress won’t be the issue. Your SERVER will be.
I would be immediately making (automatically!) nearly 300k posts, and would have to assume an (unlikely) possibility of another 200k. Each case would be one entry.
Someone else recently tried to do that on Shared Hosting and it went up in flames. You’re going to want at LEAST a good VPS for something that big.
WordPress won’t be the issue. Your SERVER will be.
And in order to build a server that suits your needs, you should get a clearer idea of what you really need.
I won’t go into detail, but as a simple example, taking your first sentence as the de-facto requirements, I could make the following assumptions. 1) Each case law is pretty much like a static page (it’s not a blog entry with lots of comments or fancy widgets). 2) You just need to server up loads of these. Based on those two, it can be served it up nice and quick with a little caching.
The devil is in the detail, and that may cost you time and money!
