Changes between Initial Version and Version 2 of Ticket #11127


Ignore:
Timestamp:
Aug 16, 2013, 2:11:15 AM (11 years ago)
Author:
Ryan J Ollos
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #11127 – Description

    initial v2  
    11Hello.
    2 I have to propose you to hear trac developers and to use @with_transaction instead db.commit() in plugin for trac 0.12. .commit() is a cause of "Database is locked" error.
     2I have to propose you to hear trac developers and to use `@with_transaction` instead `db.commit()` in plugin for trac 0.12. `db.commit()` is a cause of "Database is locked" error.
    33Example of configuration:
    44{{{
    … …  
    1616Tracchildtickets        2.5.2
    1717}}}
    18 I see this error, when I try to do "UPDATE" or "DELETE" in ITicketManupulator.validate_ticket or ITicketChangeListener.ticket_changed in my plugins. And it's gone when I had used @with_transaction in save() method in mastertickets/model.py. So I think commit() was a cause that bad interactions.
     18I see this error, when I try to do `UPDATE` or `DELETE` in `ITicketManupulator.validate_ticket` or `ITicketChangeListener.ticket_changed` in my plugins. And it's gone when I had used `@with_transaction` in `save()` method in `mastertickets/model.py`. So I think `commit()` was a cause that bad interactions.
    1919
    2020Thank you for your job. :)