[ #305330 ] dbconnector fails to work with sql server datetime lastupdate field
Date: 2006-05-21 06:24
Submitted By: Amit Karandikar (amitdk)
Assigned To: Nobody (None)
Summary: dbconnector fails to work with sql server datetime lastupdate field
Detailed description: Funambol 3.0 b3 db connector fails to work with Sql Server due to a problem
with the datetime field type stated on the "lastupdate" column of the table to
be synchronized. This same table get synchronized properly with earlier version
or version 2.3. If the field is converted to a bigint type column, updated
items are returned as item adds. I'm guessing this is related to unsuccessful
recognition of the lastupdate column type.
Date: 2006-05-29 14:36
Logged In: YES
under investigation, more log requested...
Date: 2006-05-24 17:49
Logged In: YES
When the lastupdate field is made a bigint type, the server
(or default dbconnector) is not recognizing changes made to
an existing item as a REPLACE cmd on that item for the
client on FAST SYNCS. Instead it sends back an ADD cmd for
the updated server items to the client. So in other words,
if one program updates an existing item in the database
(making sure lastupdate column gets updated), another client
synching on these database items does not get an update
callback in the C++ API. Hopefully I've tried to elaborate
the problem better. Please let me know if I need to provide
more information. However, as soon as I switch to Sync4j
2.3, the server works perfectly when items are updated by
sending REPLACE cmds on those items. So unless there is
something else wrong with the server, my initial conclusion
was that maybe the logic working with the lastupdate column
type to determine sync cmd for the item was the problem with
the 3.0 implementation.
Date: 2006-05-24 17:31
In the beta 3 version the "lastupdate" is handled as
There is not an autodetection of the type.
What does "if the field is converted to a bigint type
items are returned as item adds" mean ?
Could you upload the server log ?