|
Home > Archive > SQL Anywhere Mobile > April 2005 > Three tier Synchronization and delete.
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 |
Three tier Synchronization and delete.
|
|
| Jim Blackburn 2005-04-23, 1:24 pm |
| Hi All
ASA 9.0.2.3044
I am working on a new project that will have a three tier model and I
am have a question on how to handle deletes. I currently have a
"delflag" column on the consolidated database and use a
download_delete_curs
or event to delete the rows on the remote. This
seems to be a problem on databases that are both a consolidated and a
remote. How can I handle this situation?
Thanks.
| |
| Greg Fenton 2005-04-25, 11:23 am |
| Jim Blackburn wrote:
>
> I currently have a
> "delflag" column on the consolidated database and use a
> download_delete_curs
or event to delete the rows on the remote. This
> seems to be a problem on databases that are both a consolidated and a
> remote. How can I handle this situation?
>
One way would be to create a shadow table in the middle tier to hold the
deletes. You would download the deletes to the base table in its
download_delete_curs
or (as you currently are) *and* you would download
those same deletes to the shadow table. Then for the download to the
lowest tier, you would select from the shadow table.
Of course, and easier approach would be to synchronize the "delflag" as
an UPDATE instead of as a DELETE, but that might involve application
changes...
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/
| |
| Jim Blackburn 2005-04-25, 8:25 pm |
| On 25 Apr 2005 09:03:28 -0700, Greg Fenton
<greg. fenton_NOSPAM_@ianyw
here.com> wrote:
>Jim Blackburn wrote:
>
>One way would be to create a shadow table in the middle tier to hold the
>deletes. You would download the deletes to the base table in its
> download_delete_curs
or (as you currently are) *and* you would download
>those same deletes to the shadow table. Then for the download to the
>lowest tier, you would select from the shadow table.
>
>Of course, and easier approach would be to synchronize the "delflag" as
>an UPDATE instead of as a DELETE, but that might involve application
>changes...
Thanks Greg,
I like your second option better since I am in the middle of changing
the application anyway.
>
>Hope this helps,
>greg.fenton
|
|
|
|
|