Version: 1.0.7, by Andreas
Developer Last Online: Jan 2023
Version: 3.5.3
Rating:
Released: 08-11-2005
Last Update: 02-17-2006
Installs: 633
DB Changes Uses Plugins Template Edits
Additional Files Is in Beta Stage
No support by the author.
vBookie
Introduction
This is a Port of the original vBookie Hack created by tdjrico; full credits to him for the idea and the kind permission to port his work
A t t e n t i o n
This Hack is unsopported and incompatible with vBulletin 3.6+
You are hereby advised to not use it.
Please do not ask me about support and/or updates - there will be none.
Because 3.7.3 has some different code with 3.6.x, so you should search for calendar only, and remove the whole lines between <td ...> and </td>!You are recommended to know a little of html to do it correctly...
@all : why some of my member has a vCash of 18446744073709551416???What's wrong???
With over 12,000 bets placed and 6,000 records in some of the other tables the vbookie queries are hanging my server. Taking 10 minutes to run, it is killing our cpu.
$result = $db->query_read("
SELECT item.item_id, item.item_title, item.threadid, grp.group_title, item.item_status, item.item_created, item.item_open_until, item.item_
FROM " . TABLE_PREFIX . "vbookie_items AS item
LEFT JOIN " . TABLE_PREFIX . "vbookie_groups AS grp ON grp.group_id = item.group_id
LEFT JOIN " . TABLE_PREFIX . "thread AS thread ON thread.vbookie_item_id = item.item_id
WHERE item.item_status='".$db->escape_string($type)."'
ORDER BY $orderby item.item_id DESC
LIMIT $limit, $perpage
and this one
// Most bet-on Events
$result = $db->query_read("
SELECT item.item_id, item.item_title, item.threadid, grp.group_title, item.item_status, item.item_created, item.item_open_until, item.item_
LEFT JOIN " . TABLE_PREFIX . "vbookie_groups AS grp ON grp.group_id = item.group_id
ORDER BY item.item_n_bets_placed DESC
LIMIT 5
I wonder if I prune the data if it would help. Any thoughts?
With over 12,000 bets placed and 6,000 records in some of the other tables the vbookie queries are hanging my server. Taking 10 minutes to run, it is killing our cpu.
$result = $db->query_read("
SELECT item.item_id, item.item_title, item.threadid, grp.group_title, item.item_status, item.item_created, item.item_open_until, item.item_
FROM " . TABLE_PREFIX . "vbookie_items AS item
LEFT JOIN " . TABLE_PREFIX . "vbookie_groups AS grp ON grp.group_id = item.group_id
LEFT JOIN " . TABLE_PREFIX . "thread AS thread ON thread.vbookie_item_id = item.item_id
WHERE item.item_status='".$db->escape_string($type)."'
ORDER BY $orderby item.item_id DESC
LIMIT $limit, $perpage
and this one
// Most bet-on Events
$result = $db->query_read("
SELECT item.item_id, item.item_title, item.threadid, grp.group_title, item.item_status, item.item_created, item.item_open_until, item.item_
LEFT JOIN " . TABLE_PREFIX . "vbookie_groups AS grp ON grp.group_id = item.group_id
ORDER BY item.item_n_bets_placed DESC
LIMIT 5
I wonder if I prune the data if it would help. Any thoughts?
Seems like the same issue I am having, interesting.
Well -- not to keep talking to myself, but just to document this -- we ran that query above and created the index. So far it looks good. The table doesn't get locked when vbookie queries are running.
I will probably purge some of the bet history as well to make the data smaller. But for now things seem better.