Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Strange update conflict behavior - mySQL backend
Message
 
 
À
01/03/2007 02:04:27
Vladimir Zhuravlev
Institute of the Physics of Earth,Russia
Moscow Region, Russie
Information générale
Forum:
Visual FoxPro
Catégorie:
Client/serveur
Versions des environnements
Visual FoxPro:
VFP 8 SP1
Divers
Thread ID:
01199534
Message ID:
01199958
Vues:
16
>Hello Greg
>I have seen similar things with Oracle
>Use key field only or key+timestamp
>It will not be error in this case.
>If you need to compare also updatable fields, do it yourself
>I mean before saving data make query of the same record to new cursor and compare data you have (oldval()) with this new data from server
>If all was the same, make =tableupdate()
>If something was changed, inform user, if he wants to keeep data or change
>it on new one.

Hi Vladimir,

In the code above did you mean tablerevert() if data were not changed?
If it's not broken, fix it until it is.


My Blog
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform