Comment 1 for bug 528927
Revision history for this message
| Alexander Strebkov (alexanderstrebkov) wrote | #1 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
After some experiments:
- It is not necessary to change @Every annotation. Any change to any file in application (tested with application.conf and models) causes next job to fail with database error.
- If I browse any application page after job's database error, functionality is restored and job works again (until next modification of any project file).
- If I use @On annotation instead of @Every - everything is fine and changes doesn't cause any errors.