#1890: Can create tickets anonymously using the username of an authenticated
user
----------------------------------------+-----------------------------------
Reporter: [EMAIL PROTECTED] | Owner: cboos
Type: defect | Status: new
Priority: normal | Milestone: 0.11
Component: general | Version: 0.8.4
Severity: normal | Resolution:
Keywords: review |
----------------------------------------+-----------------------------------
Comment (by cboos):
Replying to [comment:51 [EMAIL PROTECTED]:
> Replying to [comment:46 cboos]:
> > About the `authenticated` column:
> >
> > See a TracDev/JournalingProposal#Asolution
>
> Your note on this ticket seems to imply that `is_authenticated` would
live in one of the ''n'' `ticket_change`
Sorry for being unclear then, I really meant to say that
`is_authenticated` (or simply `authenticated`) should be part of the
`journal` table.
> If this is where `is_authenticated` is going to live, it really needs to
be handled for the generalized case, though. We don't just need to know
"who did this" for tickets. It's useful for everything.
Well, yes. That was the idea, every state change in the system is a priori
done by some user, at one given point in time.
Storing that kind of information differently, redundantly and/or partially
as it's done now is a bit counter-productive.
> ... how to extract the is_authenticated flag for, say, each comment in a
ticket.
E.g. with a `property_change` and `journal` tables, like suggested in
TracDev/Proposals/Journaling:
{{{
#!python
cursor.execute("SELECT j.author, j.authenticated, j.ipnr, j.time,
p.newvalue "
" FROM property_change p "
" INNER JOIN journal j ON j.tid=p.tid"
" WHERE j.type='ticket' AND j.id=? "
" AND p.field='comment' "
" ORDER BY j.time", (ticket_id,))
for author,auth,ipnr,time,comment in cursor:
print "%s by %s (%s) %s\n\n%s\n----\n" % \
(time, author, ipnr, auth and '[authentified]' or '',
comment)
}}}
For Wiki page versions, that's a slightly different matter. Right now, the
`authenticated` column could simply be added to the `wiki` table, as
there's anyway one row for each different version.
But in the future, even this could be improved.
--
Ticket URL: <http://projects.edgewall.com/trac/ticket/1890>
The Trac Project <http://trac.edgewall.com/>
_______________________________________________
Trac-Tickets mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac-tickets
