|
Home > Archive > SQL Anywhere database replication > August 2005 > How does SQLRemote handle deleted rows?
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 |
How does SQLRemote handle deleted rows?
|
|
| Jack T. 2005-08-30, 1:23 pm |
| What happens when a remote station deletes a row, and then another station
passes in an update for that row?
Thanks,
Jack T.
| |
| Rob Waywell 2005-08-30, 8:24 pm |
| Assuming that the delete operation reaches the consolidated first, then the
row will be deleted. When the subsequent update operation reaches the
consolidated, it is applied and updates all relevant rows, which in this
case is 0 records (particularly since the update is done by primary key).
The end result is that the row is deleted at all nodes.
If the update arrives at the consolidated first, then it is applied and the
update will be replicated out to all subscribed remotes. Later when the
delete reaches the consolidated the record is deleted and the delete is
replicated out to all subscribed remotes. The end result is that the row is
deleted at all nodes.
So, what do you want to happen?
--
-----------------------------------------------
Robert Waywell
Sybase Adaptive Server Anywhere Developer - Version 8
Sybase Certified Professional
Sybase's iAnywhere Solutions
Please respond ONLY to newsgroup
EBF's and Patches: http://downloads.sybase.com
choose SQL Anywhere Studio >> change 'time frame' to all
To Submit Bug Reports:
http://case-express.sybase.com/cx/c...sc?CASETYPE=Bug
SQL Anywhere Studio Supported Platforms and Support Status
http://my.sybase.com/detail?id=1002288
Whitepapers, TechDocs, and bug fixes are all available through the iAnywhere
Developer Community at www.ianywhere.com/developer
"Jack T." <Jack. Toering_NO_SPAM_HERE
_@LeadingEdgeITA.com> wrote in message
news:4314a3b5$1@foru
ms-1-dub...
> What happens when a remote station deletes a row, and then another station
> passes in an update for that row?
>
> Thanks,
> Jack T.
>
>
>
| |
| Jack T. 2005-08-30, 8:24 pm |
| > So, what do you want to happen?
Exactly what you said. I'm trying to come up with the most set-and-forget
type replication that I can.
Thank you,
Jack T.
"Rob Waywell" <rwaywell@no_spam.ianywhere.com> wrote in message
news:4314a535$1@foru
ms-1-dub...
> Assuming that the delete operation reaches the consolidated first, then
> the row will be deleted. When the subsequent update operation reaches the
> consolidated, it is applied and updates all relevant rows, which in this
> case is 0 records (particularly since the update is done by primary key).
> The end result is that the row is deleted at all nodes.
>
> If the update arrives at the consolidated first, then it is applied and
> the update will be replicated out to all subscribed remotes. Later when
> the delete reaches the consolidated the record is deleted and the delete
> is replicated out to all subscribed remotes. The end result is that the
> row is deleted at all nodes.
>
> So, what do you want to happen?
>
> --
> -----------------------------------------------
> Robert Waywell
> Sybase Adaptive Server Anywhere Developer - Version 8
> Sybase Certified Professional
>
> Sybase's iAnywhere Solutions
>
> Please respond ONLY to newsgroup
>
> EBF's and Patches: http://downloads.sybase.com
> choose SQL Anywhere Studio >> change 'time frame' to all
>
> To Submit Bug Reports:
> http://case-express.sybase.com/cx/c...sc?CASETYPE=Bug
>
> SQL Anywhere Studio Supported Platforms and Support Status
> http://my.sybase.com/detail?id=1002288
>
> Whitepapers, TechDocs, and bug fixes are all available through the
> iAnywhere
> Developer Community at www.ianywhere.com/developer
> "Jack T." <Jack. Toering_NO_SPAM_HERE
_@LeadingEdgeITA.com> wrote in message
> news:4314a3b5$1@foru
ms-1-dub...
>
>
|
|
|
|
|