Talk:Maintenance DEV: Difference between revisions

Talk:Maintenance DEV (view source)

1 byte added , 14 May 2009

m

no edit summary

1,633

edits

@@ 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 mylist, remove file from mylist), file/ep count the same.
+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.
@@ Line 6: / Line 6: @@
-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.
+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