[RFC] Post log/record
- EXreaction
- Registered User
- Posts: 1555
- Joined: Sat Sep 10, 2005 2:15 am
[RFC] Post log/record
Much like Wikipedia or some other forum software keeps records of old posts when they are edited I believe that's probably something that should be done for 4.0. Along with better logs kept for who did what this would greatly increase accountability.
- DavidIQ
- Customisations Team Leader
- Posts: 1905
- Joined: Thu Mar 02, 2006 4:29 pm
- Location: Earth
- Contact:
Re: [RFC] Post log/record
Not sure that I agree with logging EVERY single action a user makes. That would dramatically increase database size. I guess maybe having this on som sort of switch would be fine.
- EXreaction
- Registered User
- Posts: 1555
- Joined: Sat Sep 10, 2005 2:15 am
Re: [RFC] Post log/record
I am talking about recording the changes made when editing posts. Like how revisions of wiki articles are with mediawiki.
Re: [RFC] Post log/record
At many sites posts table is the largest one already. Making it even larger by storing old post revisions will make just about everything slower and increase db size. A site I used to admin wanted to remove old posts due to perceived performance impact of having so many. I suspect there is going to be demand to make this feature optional, at least once people understand how it works.
- DavidIQ
- Customisations Team Leader
- Posts: 1905
- Joined: Thu Mar 02, 2006 4:29 pm
- Location: Earth
- Contact:
Re: [RFC] Post log/record
That is exactly what I'm talking aboutnn- wrote:At many sites posts table is the largest one already. Making it even larger by storing old post revisions will make just about everything slower and increase db size. A site I used to admin wanted to remove old posts due to perceived performance impact of having so many. I suspect there is going to be demand to make this feature optional, at least once people understand how it works.
Re: [RFC] Post log/record
On which note, if this feature does get implemented the old versions should probably be stored in a table other than posts (e.g. post_versions). This is how some other versioning software works (I don't know about Wikipedia).
Re: [RFC] Post log/record
I think this would be a very useful feature. As mentioned it should be configurable, at least an on/off switch, but I could imagine pruning options for edits/group based settings etc. And yes the data should be stored in a separate table so it does not impact query performance for regular reads.
Exreaction: Please either bring this RFC into the proper format (add it to the wiki, preferably add some more details), or move this topic to the discussion forum.
Exreaction: Please either bring this RFC into the proper format (add it to the wiki, preferably add some more details), or move this topic to the discussion forum.
Re: [RFC] Post log/record
This would be a good feature but there should be an on/off switch, a field saying maximum disk space for old posts, leave blank for unlimited (so it limit how much db space it would use and prune old ones), a button to prune from before a selected date or prune all.
Formerly known as Unknown Bliss
No unsolicited PMs please except for quotes.psoTFX wrote: I went with Olympus because as I said to the teams ... "It's been one hell of a hill to climb"
Re: [RFC] Post log/record
I would not limit the db space that it can use.. I would limit the number of revisions that are store. eg. 0 for unlimeted 1 for 1 revision and so on.. Because I doubt that all post are the same amount of db spaceUnknown Bliss wrote:This would be a good feature but there should be an on/off switch, a field saying maximum disk space for old posts, leave blank for unlimited (so it limit how much db space it would use and prune old ones), a button to prune from before a selected date or prune all.
ø = 1.618033988749895...
Everything has ø in it
Everything has ø in it
- imkingdavid
- Registered User
- Posts: 1050
- Joined: Thu Jul 30, 2009 12:06 pm
Re: [RFC] Post log/record
Agreed. You could have a max limit of, say... 5 revisions per post. Or even just 2 or something.Rotsblok wrote:I would not limit the db space that it can use.. I would limit the number of revisions that are store. eg. 0 for unlimeted 1 for 1 revision and so on.. Because I doubt that all post are the same amount of db spaceUnknown Bliss wrote:This would be a good feature but there should be an on/off switch, a field saying maximum disk space for old posts, leave blank for unlimited (so it limit how much db space it would use and prune old ones), a button to prune from before a selected date or prune all.
I think to add to this would be to give the moderator the ability to not only compare past revisions, but also to restore the post to an older revision (or a newer one, if it's already at an older revision). It could be helpful in some situations.