[yuji]

Oh interesting. Let me give this a try. Thanks for the pointer!

[yuji]

OK cool, it totally works. Thanks for the pointer! The one thing I don't understand is how to know which task id to use as the "old" task. In reading Ken's description of the naming convention, you follow the date stamp with old_id+new_id. But if I'm just adding a brand new item (not modifying an old transaction), how do I know what ID to use for the old_id?

Again, my use case here is that I plan to write a dead simple Android app that will allow me to quickly add a task directly to my webdav server, so my OmniFocus app will pick it up on the next sync.

If it all possible, I'd like to avoid having to read and parse the existing database.

[whpalmer4]

There's always a file named 0000... that is the root of the tree. Go there and follow the id links.

I compacted my database, so there was only the 0000... file, then added an action. You can how the new files were linked in in the attached screenshots.

[yuji]

Originally Posted by whpalmer4

There's always a file named 0000... that is the root of the tree. Go there and follow the id links.

I compacted my database, so there was only the 0000... file, then added an action. You can how the new files were linked in in the attached screenshots.

Awesome, thanks whpalmer4!