Ok, now that I've finally have two newly created projects working I'd figure I'd learn on how SQLite Manager works. I've been tasked with either removing a ticket complete (say, ticket #1700) or finding a way to remove a comment that exist within ticket #1700. Is the second option possible or is it better just to delete ticket #1700?
My question is, is there a problem with removing #1700 on an active Trac db? Currently we're up to 1750 and growing and here I am messing around with ticket #1700! :( Will the db know that #1700 is removed and just keep a "blank" entry for a non-existent #1700 if I choose to delete it (on an active db). I'd rather just remove the comment within the ticket rather than remove the whole ticket number, if possible. Also, what field do I look for when using the SQLite Manger on the Tables column when I decided on either removing the "comment" or the whole "ticket number?" id name source target tempPath startTime endtime state Above are just a few example fields I found in the moz_downloads table for downloads.sqlite db. And since I don't have SQLite installed yet on our Trac clients I'm just using the downloads.sqlite as an example. -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to trac-users@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
