We are using v12.01.3554. We are using both DBREMOTE and MobiLink in our setup. We occassionally have to add new tables to our publications. It seems that we always get record locks when applying these if all users are not logged out of the database.
I don't remember this being an issue in prior versions. We could make changes as long as table we are adding to publication was not already in use.
Does anyone have any insight on this behaviour?
asked 05 Nov '12, 15:39
Thanks for pointing this out Brian.
The behaviour change was introduced in v12 when we added the START/STOP SYNCHRONIZATION SCHEMA CHANGE commands, which allowed you to make schema changes to a SQL Anywhere MobiLink client without the need to have just completed a successful synchronization.
I've added a comment to the documentation for ALTER PUBLICATION on DocCommentXchange, and the documentation for the next major version should reflect the additional locks needed to perform the ALTER PUBLICATION command.
answered 07 Nov '12, 10:50