|
Home > Archive > SQL Anywhere Mobile > June 2005 > upload only, upload_script?
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 |
upload only, upload_script?
|
|
| R. van der Wiele 2005-06-02, 7:24 am |
| I want *some* tables to only dowload, not upload.
How can I achieve this the best?
Upload_cursor? If so, what qsl statement should I use (for example?: "select
* from <table> where <colomn>=<not existing value>", ps; does not work)
Thanks for any input,
Ron
| |
| Reg Domaratzki \(iAnywhere Solutions\) 2005-06-02, 7:24 am |
| What version and build number of ASA/MobiLink are you using?
Are your remote databases using ASA or UltraLite?
--
Reg Domaratzki, Sybase iAnywhere Solutions
Sybase Certified Professional - Sybase ASA Developer Version 8
Please reply only to the newsgroup
iAnywhere Developer Community : http://www.ianywhere.com/developer
iAnywhere Documentation : http://www.ianywhere.com/developer/product_manuals
ASA Patches and EBFs : http://downloads.sybase.com/swx/sdmain.stm
-> Choose SQL Anywhere Studio
-> Set "Platform Preview" and "Time Frame" to ALL
"R. van der Wiele" <r.vd.wiele@aci.nl> wrote in message
news:429efab6$1@foru
ms-2-dub...
> I want *some* tables to only dowload, not upload.
> How can I achieve this the best?
> Upload_cursor? If so, what qsl statement should I use (for example?:
" select
> * from <table> where <colomn>=<not existing value>", ps; does not work)
>
> Thanks for any input,
> Ron
>
>
| |
| R. van der Wiele 2005-06-02, 9:24 am |
| ASA Version 8.0.3.5002
All ASA
Ron
"Reg Domaratzki (iAnywhere Solutions)" <FirstName.LastName@ianywhere.com>
wrote in message news:429efc75$1@foru
ms-1-dub...
> What version and build number of ASA/MobiLink are you using?
> Are your remote databases using ASA or UltraLite?
> Reg Domaratzki, Sybase iAnywhere Solutions
| |
| Reg Domaratzki \(iAnywhere Solutions\) 2005-06-02, 9:24 am |
| Since you're using ASA on the remote, the most efficient way would be to
modify the publication you are using on the remote, so that changes are
never even sent on the wire. For example :
CREATE PUBLICATION p1 (TABLE t1, TABLE t2, TABLE t3 WHERE 1=0 );
CREATE SYNCHRONIZATION USER rem1;
CREATE SYNCHRONIZATION SUBSCRIPTION TO p1 FOR rem1 TYPE 'TCPIP' ADDRESS
'host=localhost' OPTION SV='v1';
Table t1 and t2 will upload changes, and the definition for table t3 will be
sent in the header of the synchronization, but no changes will ever be sent
from the remote, since the WHERE clause on the publication will always be
false. All three tables will download information, assuming you've defined
the proper scripts on the consolidated.
Just FYI, we do not recommend using an upload_cursor in any situation (they
have been deprecated). You should always use the upload_insert,
upload_update and upload_delete statement-based upload scripts.
--
Reg Domaratzki, Sybase iAnywhere Solutions
Sybase Certified Professional - Sybase ASA Developer Version 8
Please reply only to the newsgroup
iAnywhere Developer Community : http://www.ianywhere.com/developer
iAnywhere Documentation : http://www.ianywhere.com/developer/product_manuals
ASA Patches and EBFs : http://downloads.sybase.com/swx/sdmain.stm
-> Choose SQL Anywhere Studio
-> Set "Platform Preview" and "Time Frame" to ALL
"R. van der Wiele" <r.vd.wiele@aci.nl> wrote in message
news:429f12f9$1@foru
ms-2-dub...
> ASA Version 8.0.3.5002
> All ASA
> Ron
>
> "Reg Domaratzki (iAnywhere Solutions)" <FirstName.LastName@ianywhere.com>
> wrote in message news:429efc75$1@foru
ms-1-dub...
>
>
|
|
|
|
|