taskGNU Thales - Tasks: task #3030, Keep track of nick changes

 
 

You are not allowed to post comments on this tracker with your current authentication level.

task #3030: Keep track of nick changes

Submitter:  Lucas Nussbaum <lnu>
Submitted:  Sat 10 Jan 2004 11:28:21 PM UTC
   
 
Category:  Thales Should Start On:  Sat 10 Jan 2004 12:00:00 AM UTC
Should be Finished on:  Sat 31 Jan 2004 12:00:00 AM UTC Priority:  1 - Later
Status:  None Privacy:  Public
Assigned to:  None Percent Complete:  0%
Open/Closed:  Open Effort:  0.00

Fri 16 Jan 2004 10:07:15 PM UTC, comment #1: 

I'm still looking for a clean way to implement this. Is something working like an history is really needed ? I'm not sure.

Lucas Nussbaum <lnu>
Group Member
Sat 10 Jan 2004 11:28:21 PM UTC, original submission:  


>>4. It would be also nice if Thales kept track of what happened to the
>>user, i.e. two columns like "what" and "what_data", so that for
>>example:
>> what -> change; what_data -> newnick
>> what -> quit; what_data -> quit reason
>
>added to my todo list, with a "quittime" field.


Also add an optional cache for nick changes :)
It would make the database HUGE, but Discussioni is small (peak of
95~105 users at night) so I could use it :P

Lucas Nussbaum <lnu>
Group Member

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

CC list is empty

 

There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

 

Follow 2 latest changes.

Date Changed by Updated Field Previous Value => Replaced by
2004-01-16 lnu CategoryThales documentation Thales
    Priority5 - Normal 1 - Later

Back to the top

Powered by Savane 3.13-d3ae.
Corresponding source code