| Maggie 2005-04-19, 9:24 am |
| Thanks for the Response.
If We create an Another Unique Key like Autonumber, It will
create the dublicated data in the Server. Since more than a
client may create the same Ident with the same name, Since
the Unique Key generated it will store the Same Ident as the
another record. this will create the lot of Idents Like
this. What we want to that is The same ident is already
exists in the Consolidated Server.Why the Mobilink Server is
not updating instead it is trying to Insert the New Record.
Is ther any option to Solve this issue apart from creating
the separate Unique id.
Ex.
Client 1 ---> New1 as Ident ----> Consolidated ( If Exists
Update or Insert)
Client 2 ---> New1 as Ident ----> Consolidated ( If Exists
Update or Insert)
Each client will be a different mobilink User ( Unique ID )
It work's fine for the single user. i.e it will update the
same ident after some modification done by the same user.
Kindly Help us to solve this problems. as a temprory we have
disabled the uploding part in our script.
With regds,
Maggie
> Maggie wrote:
>
> This is something that you absolutely must *design* your
> distributed application *not* to do. Primary keys must
> be generated such that they are unique across *all*
> database nodes. There are a number of strategies you can
> use to accomplish this:
>
> - Global Autoincrement (recommended for most situations)
> - UUIDs (also known as GUIDs)
> - Key Pools
> - Composite Keys
>
>
> If this is an urgent matter (which it appears to be), you
> should open a case with iAnywhere Technical Support. The
> newsgroups are not an official support channel and are
> run on a voluntary basis.
>
>
>
http://www.ianywhere.com/support/co...ct_support.html
>
> greg.fenton
> --
> Greg Fenton
> Consultant, Solution Services, iAnywhere Solutions
> --------
> Visit the iAnywhere Solutions Developer Community
> Whitepapers, TechDocs, Downloads
> http://www.ianywhere.com/developer/
|