This was exactly what was wrong! I just followed your instructions and everything is now working perfectly! To show my gratefulness, I'm passing a virtual bottle of single malt in you direction!
;-D Hans On 21 Okt, 09:07, Robert Buchholz <[email protected]> wrote: > On Tuesday 19 October 2010, Hans K. Aspenberg wrote: > > > We just changed our Agilo (1.3.0.7 running on Trac 0.11.7, Python > > 2.5) from SQLITE to PostGreSQL to get rid of multitasking problems. > > PostgreSQL helped fro those, but then other problems arised. When > > updating a task and entering s number in "remaining_time", Agilo > > traps generating the following DEBUG log: > > It seems the sequence for automatically generating ids is off. On a psql > console, please run: > SELECT MAX(id) FROM agilo_burndown_data_change; > SELECT * from agilo_burndown_data_change_id_seq; > > if last_value in the second query is smaller than MAX(id), try setting > it to a higher value: > UPDATE agilo_burndown_data_change_id_seq SET last_value = 1234; > > Cheers > Robert -- Follow Agilo on Twitter: http://twitter.com/agiloforscrum Please support us by reviewing and voting on: http://userstories.com/products/8-agilo-for-scrum http://ohloh.net/p/agilo-scrum http://freshmeat.net/projects/agiloforscrum You have received this message because you are subscribed to the "Agilo for Scrum" Google Group. This group is focused on supporting Agilo for Scrum users and is moderated by Agilo Software GmbH <http://www.agiloforscrum.com>. To post to this group, send email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/agilo
