Home > Archive > SQL Anywhere Mobile > October 2005 > Publication question









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 Publication question
Alexey Panshin

2005-10-27, 8:20 am

Hi
I have an ASA database which acts as Mobilink client twice with two
consolidated database
( i use ASA version 9.0.2.3193).
I have two different publications and two diferent synchronization
users/subscriptions for it.
But if column subset in one publicatiom differs from another this error
message appears:

E. 10/11 16:15:06. Publications main and so have a column subset mismatch on
table Partners.
E. 10/11 16:15:06. No synchronization can occur until this mismatch is
resolved.

Can i synchronize two publications with different column subset any way?

regards, Alexey


David Fishburn

2005-10-27, 8:21 am

"Alexey Panshin" <lesha@unact.ru> wrote in news:434cd54b@forums
-2-dub of
sybase.public.sqlanywhere.mobilink:

AP> I have an ASA database which acts as Mobilink client twice with two
AP> consolidated database
AP> ( i use ASA version 9.0.2.3193).
AP> I have two different publications and two diferent synchronization
AP> users/subscriptions for it.
AP> But if column subset in one publicatiom differs from another this
AP> error message appears:
AP>
AP> E. 10/11 16:15:06. Publications main and so have a column subset
AP> mismatch on table Partners.
AP> E. 10/11 16:15:06. No synchronization can occur until this mismatch
is
AP> resolved.

I have confirmed. You canNOT synchronize a subset 1 table between two
different servers.

AP> Can i synchronize two publications with different column subset any
AP> way?

In Jasper, this will be possible with script based uploads (this is
similar to writing download_cursors on the server side).

In the 9.x version, you have two techniques I can think of.
1. Upload the entire table to each consolidated. But upload the
changes into a temporary table. Using the upload_end event for that
table, call a stored procedure that does the appropriate action for
each row in the temporary table. Delete the rows when finished.
2. Create a shadow table on the remote and maintain it with triggers.
This gets a bit more complicated since you might have to synchronize
with trigger actions on.

--
David Fishburn
Certified ASA Developer Version 8
iAnywhere Solutions - Sybase
Professional Services
Please only post to the newsgroup
Please ALWAYS include version and MORE importantly BUILD number with
EACH post (dbeng9 -v).

EBFs and Maintenance Releases
http://downloads.sybase.com/swx/sdmain.stm

Developer Community / Whitepapers
http://www.ianywhere.com/developer

CaseXpress - to report bugs
http://casexpress.sybase.com

CodeXchange - Free samples
[url]http://ianywhere.codexchange.sybase.com/servlets/ ProjectDocumentList[
/url]

Sponsored Links





Also available: Server administration forum archive | Web Design forum archive | Software forum archive | Hardware reviews archive | Programming forum archive

Copyright 2008 droptable.com