vb.org Archive

vb.org Archive (https://vborg.vbsupport.ru/index.php)
-   vB3 Programming Discussions (https://vborg.vbsupport.ru/forumdisplay.php?f=15)
-   -   Documentation for the Vbulletin Database Schema? (https://vborg.vbsupport.ru/showthread.php?t=172858)

Cereskun 03-12-2008 11:23 PM

Documentation for the Vbulletin Database Schema?
 
Is there documentation that can tell a developer what each column in a table does?

For example, what does the "dateline" column in the vb_thread table store? Is it using Unix time? Not all columns seem to be named so that their purpose is obvious.

Thanks.

Dismounted 03-13-2008 05:34 AM

"dateline" is pretty self-explanatory. It stores the time the thread was created as a UNIX timestamp.

Cereskun 03-13-2008 07:27 AM

Thank you for that.

I would argue that it isn't that self explanatory for someone who isn't used to the vBulletin way of doing things. Do I take that as a "no", that there isn't documentation for this?

Dismounted 03-13-2008 11:32 AM

Well, you just have to experiment with things to see how they work. That's how I got to know vBulletin.

Lynne 03-13-2008 01:54 PM

Quote:

Originally Posted by Cereskun (Post 1463618)
Do I take that as a "no", that there isn't documentation for this?

I do not know of any documentation and have never seen anyone talk about seeing any documentation for this either.

Opserty 03-13-2008 02:52 PM

Just check the scripts, if vBulletin fetches data from the database it will normally have the column as the array key for that piece of data (if it is in an array). When vBulletin is setting data it normally uses the column names as the value for the HTML name="..." attribute on the form inputs.

You just have to look around and see what is going on. You could also just set up a test installation and check out the contents of the database, once you know what data is stored just find the corresponding data which is displayed.

Cereskun 03-13-2008 07:15 PM

Alright, I just thought there might have been an easier way to figure this all out. Some of the columns aren't returning the results I expected when I am querying them directly.

Thanks for the pointers.

nexialys 03-13-2008 07:37 PM

there is a way to ask for documentation, on the official website... here is a site for modifications... most of the guys that are modding here are aware of the protocols, or at least try to read the code before the panic... you can't expect to work for vBulletin if you have no idea of how PHP works... dateline is self-explanatory for me, as it's a general term in php for unix-dateline


All times are GMT. The time now is 04:34 AM.

Powered by vBulletin® Version 3.8.12 by vBS
Copyright ©2000 - 2025, vBulletin Solutions Inc.

X vBulletin 3.8.12 by vBS Debug Information
  • Page Generation 0.01587 seconds
  • Memory Usage 1,717KB
  • Queries Executed 10 (?)
More Information
Template Usage:
  • (1)ad_footer_end
  • (1)ad_footer_start
  • (1)ad_header_end
  • (1)ad_header_logo
  • (1)ad_navbar_below
  • (1)bbcode_quote_printable
  • (1)footer
  • (1)gobutton
  • (1)header
  • (1)headinclude
  • (6)option
  • (1)post_thanks_navbar_search
  • (1)printthread
  • (8)printthreadbit
  • (1)spacer_close
  • (1)spacer_open 

Phrase Groups Available:
  • global
  • postbit
  • showthread
Included Files:
  • ./printthread.php
  • ./global.php
  • ./includes/init.php
  • ./includes/class_core.php
  • ./includes/config.php
  • ./includes/functions.php
  • ./includes/class_hook.php
  • ./includes/modsystem_functions.php
  • ./includes/class_bbcode_alt.php
  • ./includes/class_bbcode.php
  • ./includes/functions_bigthree.php 

Hooks Called:
  • init_startup
  • init_startup_session_setup_start
  • init_startup_session_setup_complete
  • cache_permissions
  • fetch_threadinfo_query
  • fetch_threadinfo
  • fetch_foruminfo
  • style_fetch
  • cache_templates
  • global_start
  • parse_templates
  • global_setup_complete
  • printthread_start
  • bbcode_fetch_tags
  • bbcode_create
  • bbcode_parse_start
  • bbcode_parse_complete_precache
  • bbcode_parse_complete
  • printthread_post
  • printthread_complete