Re^3: RFC: a nodetype for considerations (history)

Wait, the node history table isn't tied to edits. I'm not talking about "recent janitorial edits". I'm talking about the node history table that records node approval, move, consideration, unconsideration, etc. I'd rather not have comments tied to considerations since approval and moving don't require consideration. But whatever works. (:

- tye

Comment on Re^3: RFC: a nodetype for considerations (history)

Replies are listed 'Best First'.
Re^4: RFC: a nodetype for considerations (history) by Arunbear (Prior) on Dec 03, 2006 at 22:58 UTC
Thanks for clarifying that. Taking a look at castaway's notes (and demerphq's comments of 2005-10-12) in the pmdev wiki, the only table similar (though less functional) to what you've described above is approvalhistory. Is the node history table meant to supersede approvalhistory? If so, can you create it?	[reply]
Re^5: RFC: a nodetype for considerations (approvalhistory+tinytext) by tye (Sage) on Dec 04, 2006 at 01:35 UTC
I think it'd be good to add a small text column to approvalhistory for comments ('tinytext' allows up to 256 bytes). I'm not sure what all you plan to use this for, but would that cover it? - tye	[reply]