History of TP-DB-Hits

tiki_object_access_ (content_id is primary key):
content_id, hits, external_hits, bandwidth, aggregate_bandwidth, count_start_date, last_access_ip, last_access_session

This table is used for keeping track of access by users to tiki objects. This table is expected to be updated for every access to tikipro page

Content_ID - integer - Info on actual content and link to tiki_content table

Hits - long integer- Total number of times the object has been accessed

External_Hits - long integer - Total number of times the object has been accessed where such access was not result of reference from another object on the same site

Bandwidth - long_integer - Total amount of bandwidth (in bytes) that was consumed during all accesses to it

Aggregate_Bandwidth - long integer - Total amount of bandwidth that was consumed during all access to the oject including any bandwidth consumed for sending any attached/linked/related objects which are hit as a result of accessing this object

Count_Start_Date= - datetime - The first time the page was accessed, when counting of hits began

Last_Access_IP= - long integer or varchar - IP address of the last system that accessed the page (as an option to site administrator in case of consequitive accsses from the same ip with same session, such hit would not be counted as its then just a refresh)

Last_Access_Session= - integer? - id of the session that accessed the page (used together with Last_Access_IP to prevent counting of page refreshes as hits)

This table would replace hits field in various other tables such as tiki_content, tiki_structures, tiki_blogs, tiki_attachments.

The hits would be counted by every page access and table updated as one operation for all the objects that were accessed (so as to minimize number of updates to database). Optional quota package would also allow counting bandwidth used during such access

tiki_content_access_ (content_id is primary key):
content_id, hits, external_hits, bandwidth, aggregate_bandwidth, count_start_date, last_access_ip, last_access_session

This table is used for keeping track of access by users to tiki objects. This table is expected to be updated for every access to bitweaver page

Content_ID - integer - Info on actual content and link to tiki_content table

Hits - long integer- Total number of times the object has been accessed

External_Hits - long integer - Total number of times the object has been accessed where such access was not result of reference from another object on the same site

Bandwidth - long_integer - Total amount of bandwidth (in bytes) that was consumed during all accesses to it

Aggregate_Bandwidth - long integer - Total amount of bandwidth that was consumed during all access to the oject including any bandwidth consumed for sending any attached/linked/related objects which are hit as a result of accessing this object

Count_Start_Date= - datetime - The first time the page was accessed, when counting of hits began

Last_Access_IP= - long integer or varchar - IP address of the last system that accessed the page (as an option to site administrator in case of consequitive accsses from the same ip with same session, such hit would not be counted as its then just a refresh)

Last_Access_Session= - integer? - id of the session that accessed the page (used together with Last_Access_IP to prevent counting of page refreshes as hits)

This table would replace hits field in various other tables such as tiki_content, tiki_structures, tiki_blogs, tiki_attachments.

The hits would be counted by every page access and table updated as one operation for all the objects that were accessed (so as to minimize number of updates to database). Optional quota package (or other comparable package) can also allow counting bandwidth used during such access