Beefy Boxes and Bandwidth Generously Provided by pair Networks
The stupid question is the question not asked

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

by Arunbear (Prior)
on Nov 28, 2006 at 22:37 UTC ( #586583=note: print w/replies, xml ) Need Help??

in reply to Re: RFC: a nodetype for considerations (history)
in thread RFC: a nodetype for considerations

Some considerations (e.g. for reaping) don't result in an edit but still need a janitor comment, which is why I think the comment should be stored with the consideration rather than in the node history table.
  • Comment on Re^2: RFC: a nodetype for considerations (history)

Replies are listed 'Best First'.
Re^3: RFC: a nodetype for considerations (history)
by tye (Sage) on Nov 28, 2006 at 23:02 UTC

    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        

      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?

        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        

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://586583]
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others examining the Monastery: (3)
As of 2021-04-14 04:01 GMT
Find Nodes?
    Voting Booth?

    No recent polls found