Download & Extend
Flag Abuse » Issues

Use separate table for storing whitelisted content

Posted by q0rban on February 26, 2011 at 9:49pm
Project:Flag Abuse
Version:7.x-2.x-dev
Component:Code
Category:task
Priority:major
Assigned:Unassigned
Status:needs review

Issue Summary

Currently the abuse flag settings are stored in the variable table with a separate row for each admin operation. This could cause quite a performance concern for a site with large amounts of content. A separate table should be used to store this data.

Login or register to post comments

Comments

#1

Posted by q0rban on February 26, 2011 at 9:50pm
Assigned to:Anonymous» q0rban

#2

Posted by q0rban on February 15, 2012 at 7:36pm
Priority:normal» major
Assigned to:q0rban» Anonymous

Bumping this up to major and un-assigning myself.

#3

Posted by q0rban on February 16, 2012 at 4:51pm
Title:Use separate table for storage» Use separate table for storing whitelisted content
Status:active» needs review

Ok, here's a first pass at this. I'd like to get some people to test this with real data, as unfortunately I don't have any yet. :/

AttachmentSize
flag-1074242-whitelist-db-storage-3.patch 8.13 KB

#4

Posted by q0rban on February 16, 2012 at 5:12pm

Take 2.

AttachmentSize
flag-abuse-1074242-whitelist-db-storage-4.patch 8.23 KB
nobody click here