Competitor table won't update a competitor's details

[Ken McLean]

Competitor table won't update a competitor's details. Trying to change a competitor's FirstName won't update the CSV (even though the GUI is updated). Reloading the CompetitorTable shows the old value

[Craig Mahony (cmahony)]

I find that the competitors details do save. However you need to be aware of the current timing of the file watcher that only saves every 10 seconds or whatever it gets set to. I have been using 2 minutes so input is not so interrupted. If the Application is closed before filewatcher flushes any data then the data is lost.

[Ken McLean (kenmclean)]

Well then that is the bug. Filewatcher should have an override priority on the application shutdown, so that nothing is lost.

[Craig Mahony (cmahony)]

This is related the the filewatcher thread that does the flushQueue. If you
wait long enough the name does update to file.

Craig
----- Original Message -----
From: "Launchpad Bug Tracker" <email address hidden>
To: <email address hidden>
Sent: Friday, February 06, 2009 10:50 PM
Subject: [Bug 313411] [NEW] Competitor table won't update a
competitor'sdetails

You have been subscribed to a public bug:

Competitor table won't update a competitor's details. Trying to change a
competitor's FirstName won't update the CSV (even though the GUI is
updated). Reloading the CompetitorTable shows the old value

** Affects: openscore
     Importance: Medium
     Assignee: Craig Mahony (cmahony)
         Status: New

--
Competitor table won't update a competitor's details
https://bugs.launchpad.net/bugs/313411
You received this bug notification because you are a bug assignee.

[Craig Mahony (cmahony)]

Agreed. This then needs re-allocation to Tudor.

[Ken McLean (kenmclean)]

Reassigned to Tudor

[Craig Mahony (cmahony)]

This is working fine for me at the moment. Please re-test to confirm.

[Craig Mahony (cmahony)]

I believe this is now working.

[Ken McLean (kenmclean)]

This seems to be working, but in a networked env it's a bit touch and go due to the write queue. As such it requires a solution to bug #368576 to be truly fixed.