From: Evan R. <eva...@he...> - 2008-04-22 12:26:04
|
Hey Luigia, I do set those values in both the calendar and contact tables, but performing a sync still fails to detect those entries. What I have noticed is that the last_update value is different between the webdemo and my update statements. I am inserting UNIX_TIMESTAMP() * 1000 into the last_update field. For instance, this morning it inserted 1208867003000 (April 22, 2008, 8:23AM EST). Status = 'U' However, when I do an update to the same record through the webdemo I get a last_update of 1208849001973, (April 22, 2008, 3:23am EST, or 723am GMT). Status = 'U' Is this what is causing my problem? It seems like even if I wait to sync, it still won't detect the changes. I can't find anything different in the records before/after the webdemo or my web client updates the record. Thanks for the help! I know there's some funny business in my code, but I'm just having a trouble tracking it down. Thanks! E -----Original Message----- From: syn...@li... [mailto:syn...@li...] On Behalf Of Luigia Fassina Sent: Tuesday, April 22, 2008 3:09 AM To: syn...@li... Subject: Re: [funambol-users] Correct Last_Update entry Hi, to detect the modified calendars are used the values in the columns last_update and status in fnbl_pim_calendar. The last_update field is updated with the modification time (that is not the sync time) and the status is updated according to the modification type (N means new item, U item updated and D item deleted). You could try to use the webdemo client (http://<your-server>:<your-port>/webdemo) to see what happens in the database. bye Luigia |