Hi All, I have written a small desktop app that I use for tracks. Currently just use dropbox to keep sqlite databse file sync'd across machines which is a bit of a fudge and I occasionally get conflicts due to using a netbook offline quite a bit.
I was writing a script that would sync a local db to a tracks server using the api. It was syncing contexts and projects quite well using updated-at to detect changes but has come unstuck on todos because I don't seem to be able to write updated-at to a todo consistently, the server is overwriting it with the current time (although it occasionally does work, which is odd). As it has changed the field the two db's aren't sync'd and I detect the changes on the server. I can probably work around this by doing two syncs in a row but I would prefer to keep the original updated-at value. E.g. If I post this old todo to the api the updated-at field will be changed to todays date. When I do similar with a project it will keep the old value. <todo> <context-id>481</context-id> <project-id>713</project-id> <description>Add aero bling in windows(tm)</description> <created-at>2010-08-13 13:19:13</created-at> <completed-at>2010-08-13 13:19:17</completed-at> <state>completed</state> <updated-at>2010-08-13 13:19:17</updated-at> </todo> So question is: What is the intended behavior, should I be able to write to the updated-at field? If I should be able to, any ideas on why it is not working on todos? Cheers, Steve
_______________________________________________ Tracks-discuss mailing list [email protected] http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
