From what I can gather the new vB5 uses one table to store all the data, is this correct?
Announcement
Collapse
No announcement yet.
What is the database stucture like?
Collapse
X
-
200 tables.Shamil Nunhuck, - Radon Systems Ltd.
█ VPS + Dedicated Server Hosting and Management
█ vBulletin Hosting and Services
█ Server / Website Consultation
Comment
-
Originally posted by Marco Mamdouh View PostNot a one table for the whole vBulletin script, But there's a one table for all of the content and it's called "node" so forums and threads ... etc are nodes.
Could you explain a little bit more regarding this 'node' table. It must have many fields to be able to combine several tables that were once separate tables in vB4.
It would be interesting to know what tables were combined into this one 'node' table.
Comment
-
Originally posted by Andy View PostThank you Mamdouh and Shamil.
Could you explain a little bit more regarding this 'node' table. It must have many fields to be able to combine several tables that were once separate tables in vB4.
It would be interesting to know what tables were combined into this one 'node' table.
However in a short answer is yes, There's 54 fields in node table that controls the node viewing operation, And there's content type and routes which are controlling what is this node belong to.
Comment
-
Thank you Marco.
Is this node table just like any other table in mySQL, meaning it has rows and fields.
Could you expand explain a little bit what you mean by "And there's content type and routes which are controlling what is this node belong to".
Comment
-
Originally posted by Andy View PostThank you Marco.
Is this node table just like any other table in mySQL, meaning it has rows and fields.
Could you expand explain a little bit what you mean by "And there's content type and routes which are controlling what is this node belong to".
If you've got the publishing suite, it's EXACTLY the same idea on the CMS. Sections/Articles were both nodes, but articles have a separate table that contained the text information.
Comment
-
Thanks Dead Eddie. I don't have the suite so not able to see what you mean.
How does a node table define a structure? Perhaps an example of how a thread information is stored. You have the threadid, postid and pagetext, how is it different now?
Comment
-
Think of the structure your forum. You've got categories, forums under those categories, threads within the forums, and posts within the threads. Within 5, the first 3 are contained entirely within the node table.
Posts also sit on the node table, but because there is extra information needed to store posts (e.g. the post text), the extra information is stored within a new "text" table that is used for all the other text content types (blog posts, private messages, comments).
So, category is a node, forum is a node, thread is a node, and post is a node joined to text.
Comment
-
Originally posted by Dead Eddie View Post
Posts also sit on the node table, but because there is extra information needed to store posts (e.g. the post text), the extra information is stored within a new "text" table that is used for all the other text content types (blog posts, private messages, comments).
Thank you Eddie.
Comment
-
-
Originally posted by pokesph View Postnodes as in Drupal type nodes?
If you wanted to compare to something, I'd compare with the vb4 CMS nodes. The database structure is virtually identical.
Comment
widgetinstance 262 (Related Topics) skipped due to lack of content & hide_module_if_empty option.
Comment