Yes, just pass the "when" parameter to save_changes().
--Noah
[EMAIL PROTECTED] wrote:
Yeah. I know. But still: it's not a monumental change and more robustness
is never a bad thing.
Besides; should I chose to change my interaction to be proper and use the
ticket-model, would it then support custom timestamp on the comment like I
require?
/Philip
You should not be altering the database directly at all. Use the Ticket
model object.
--Noah
[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.
2. Alter the code so that oldvalue='<replied to>.<current>' is changed
to
use relative numbers such as '-1.0'.
I hope this request won't upset the code base too much. It would make
the
database robust to changes where comments are inserted at the top or
bottom.
Alternatively an auto_increment row ID could be added and used for
referencing. That would make the database completely robust and allow
sorting the changelog by author, for instance.
Any comment on this?
/Philip
_______________________________________________
Trac-dev mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac-dev
_______________________________________________
Trac-dev mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac-dev
_______________________________________________
Trac-dev mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac-dev
_______________________________________________
Trac-dev mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac-dev
