Talk:Maintenance DEV: Difference between revisions
Fahrenheit (talk | contribs) (New page: Hmm, don't know if this is actually useful, but a mix of DirtyBlock and update some of the stats on the stats on the fly would probably be the best alternative, the slave doesn't sound ver...) |
mNo edit summary |
||
| (2 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
Hmm, don't know if this is actually useful, but a mix of DirtyBlock and update some of the stats on the stats on the fly would probably be the best alternative, the slave doesn't sound very good.. | Hmm, don't know if this is actually useful, but a mix of DirtyBlock and update some of the stats on the stats on the fly would probably be the best alternative, the slave doesn't sound very good... | ||
The user stats for an anime/ep/file could be probably be calculated on event (add file to | The user stats for an anime/ep/file could be probably be calculated on event (add file to MyList, remove file from MyList), file/ep count the same. | ||
group stats could use the dirty block, no loss there. | group stats could use the dirty block, no loss there. | ||
Though the trigger issues brought up is tricky indeed... | |||
User stats is the main problem, definitely dirty block here, but I would make the added to DB stuff on event (add/remove anime, last anime added to MyList, date of last MyList addition) the rest I would make on request of info, the user probably won't request the data much so no much need to update that data that often. | |||
Though the trigger issues brought up is tricky indeed... -fahrenheit | |||
Latest revision as of 09:22, 14 May 2009
Hmm, don't know if this is actually useful, but a mix of DirtyBlock and update some of the stats on the stats on the fly would probably be the best alternative, the slave doesn't sound very good... The user stats for an anime/ep/file could be probably be calculated on event (add file to MyList, remove file from MyList), file/ep count the same.
group stats could use the dirty block, no loss there.
User stats is the main problem, definitely dirty block here, but I would make the added to DB stuff on event (add/remove anime, last anime added to MyList, date of last MyList addition) the rest I would make on request of info, the user probably won't request the data much so no much need to update that data that often.
Though the trigger issues brought up is tricky indeed... -fahrenheit