The easiest way, for me, was to dump the database and remove the
offending entry.
Like this:
echo .dump | sqlite3 trac.db >trac.dump20110211
remove this line from trac.dump20110211:
INSERT INTO "subtickets" VALUES('261','261');
and then remake the database:
sqlite3 htt
On Wed, 2011-02-09 at 08:32 -0500, Chris Nelson wrote:
> Roger Oberholtzer wrote:
> >...
> >> If you open the Trac database (which will depend on various
> >> installation-specific settings), you can do:
> >>
> >>DELETE FROM subtickets WHERE parent=child;
> >
> > You make it look so simple. I
On 02/09/2011 08:26 AM, Roger Oberholtzer wrote:
I am guessing I can do this via the sqlite3 command?
Yes.
I am never sure
about the BEGIN TRANSACTION / COMMIT stuff. Do I need to put that around
the DELETE statement?
Only if you care about being able to roll back a set of commands if one
Roger Oberholtzer wrote:
>...
>> If you open the Trac database (which will depend on various
>> installation-specific settings), you can do:
>>
>>DELETE FROM subtickets WHERE parent=child;
>
> You make it look so simple. I really need to improve my SQL skills.
I can never remember the comman
On Wed, 2011-02-09 at 08:03 -0500, Chris Nelson wrote:
>
> > Is all this in trac.db?
>
> Yes, the table is in trac.db. In the plugin's db_default.py you can
> find:
>
>from trac.db import Table, Column
>
>name = 'subtickets'
>version = 1
>tables = [
>Table(name, key=('
Roger Oberholtzer wrote:
> On Tue, 2011-02-08 at 11:31 -0500, Chris Nelson wrote:
>
>>> Any idea how I could remove this value from the problem ticket? I am
>>> guessing I need to use some SQL. And here is where my knowledge
>>> ends.
>>
>> The subtickets relation (table) is much like the master
On Tue, 2011-02-08 at 11:31 -0500, Chris Nelson wrote:
> > Any idea how I could remove this value from the problem ticket? I am
> > guessing I need to use some SQL. And here is where my knowledge ends.
>
> The subtickets relation (table) is much like the mastertickets relation.
> Remove any row w
Roger Oberholtzer wrote:
> On Tue, 2011-02-08 at 08:52 -0500, Chris Nelson wrote:
>> Roger Oberholtzer wrote:
>>> I have added the sub-ticket macro from Trac Hacks and am looking
>>> forward to using it. I would like to investigate reorganizing some
>>> tickets to have this relationship. It appears
On Tue, 2011-02-08 at 08:52 -0500, Chris Nelson wrote:
> Roger Oberholtzer wrote:
> > I have added the sub-ticket macro from Trac Hacks and am looking
> > forward to using it. I would like to investigate reorganizing some
> > tickets to have this relationship. It appears to me that a sub-ticket
> >
Roger Oberholtzer wrote:
> I have added the sub-ticket macro from Trac Hacks and am looking
> forward to using it. I would like to investigate reorganizing some
> tickets to have this relationship. It appears to me that a sub-ticket
> added to a ticket must be a new ticket added via the 'add' butto
I have added the sub-ticket macro from Trac Hacks and am looking forward
to using it. I would like to investigate reorganizing some tickets to
have this relationship. It appears to me that a sub-ticket added to a
ticket must be a new ticket added via the 'add' button. Is that the only
way? Is ther
11 matches
Mail list logo
