| Breck Carter [TeamSybase] 2005-09-22, 9:23 am |
| Yes or no: In an upload-only scenario, does specifying -e uo=ON
eliminate the need to specify lt=OFF?
Or is it necessary to specify lt=OFF to avoid errors like this?
SQL statement failed: (-210) User 'xxx' has the row in 'ttt'
locked.
Yes or no: Will it still do the update tracking described below, if -e
uo=ON?
=====
MobiLink Clients
Adaptive Server Anywhere Clients
Initiating synchronization
Concurrency during synchronization
....
On all platforms except Windows CE, by default, dbmlsync obtains a
shared lock on all tables mentioned in any publication being
synchronized.
....
An alternative way to protect data integrity is to set the extended
option LockTables to OFF, which prevents an article's tables from
being locked. This causes dbmlsync to track all rows that are modified
after the upload stream has been built.
=====
Breck
--
SQL Anywhere Studio 9 Developer's Guide
Buy the book: http://www.amazon.com/exec/obidos/A...7/risingroad-20
bcarter@risingroad.com
RisingRoad SQL Anywhere and MobiLink Professional Services
www.risingroad.com
|