[EMAIL PROTECTED] wrote:
Hi,
I insert my own comments directly into the database with a cronjob. This
causes a lot of problems with the new reply-feature (which is great by the
way!). Mainly the issue is that inserting an old or future comment (to
force its placement at top or bottom) will break the numbering scheme.
So I ask two things:
1. Alter the code so that oldvalue='<NUM>' will not be set, since it seems
not to be needed for anything.
It is now, since http://projects.edgewall.com/trac/changeset/3468
I modified grouped_changelog_entries() to also take an option `when`
argument. Then, not all the change groups are retrieved, only the one
corresponding to the given time. Then, I _have to_ rely on the change's
sequence number, which is currently stored in the comment oldvalue.
2. Alter the code so that oldvalue='<replied to>.<current>' is changed to
use relative numbers such as '-1.0'.
A better replacement would be to have real identifiers for changes.
See
http://projects.edgewall.com/trac/wiki/TracDev/JournalingProposal#Asolution
(hum, I should have named that TracDev/Proposals/Journaling ...).
With this, the replyto information could be stored in a field of its own,
and it could contain the tid of the change.
I'm afraid this will have to wait 0.11 ...
-- Christian
_______________________________________________
Trac-dev mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac-dev
