|
Home > Archive > SQL Anywhere Mobile > April 2006 > What happend - conflict.
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
What happend - conflict.
|
|
| Fantom 2006-04-06, 8:28 pm |
| What happend when i write only scripts upload_insert, upload_update and
upload_delete, and two remote database change this same record ?
When firs synch record from first user is update.
When second synch, record from second user is update too ?
Fantom
ps. And when i add script upload_fetch etc i may resolve conflicts ? But
when this scripts is no exists, conflict is not detected and records is
always updated ?
| |
| Greg Fenton 2006-04-06, 8:28 pm |
| Fantom wrote:
> When second synch, record from second user is update too ?
Yes. This is called "last one to synch wins".
> ps. And when i add script upload_fetch etc i may resolve conflicts ? But
> when this scripts is no exists, conflict is not detected and records is
> always updated ?
Writing upload_fetch will allow ML to identify a conflict, but it will
not resolve it.
For that you need to write upload_old_row_inser
t, upload_new_row_inser
t
and resolve_conflict scripts. Alternatively, you can use the fully
parametarized upload_update script (providing "?" for both old row and
new row values...but this can be tedious).
In the SQLAnywhere 9.x docs, see:
MobiLink Administration Guide
Synchronization Techniques
- Handling conflicts
Hope this helps,
greg.fenton
--
Greg Fenton
Consultant, Solution Services, iAnywhere Solutions
--------
Visit the iAnywhere Solutions Developer Community
Whitepapers, TechDocs, Downloads
http://www.ianywhere.com/developer/
|
|
|
|
|