FORUMS PROFESSIONNELS
WINDEV
,
WEBDEV
et
WINDEV Mobile
Accueil
|
Messages récents
|
Connexion
|
Déconnexion
|
Français
Accueil
→
WINDEV 2024
→
substituting CLEUNIKs in child records
substituting CLEUNIKs in child records
Débuté par Brian Pottorff, 19 juin 2001 16:06 - 4 réponses
Connectez-vous…
Brian Pottorff
#1
Posté le 19 juin 2001 - 16:06
Are there any good reasons why one should not change a child record's
parent by substituting CLEUNIKs that exist already?
Signaler
0
0
Gill Davis
#2
Posté le 20 juin 2001 - 10:49
Hi Brian.
Answer: NO
I copy over keys as necessary as false IDs to have the 'wrong' file
bring up its adopted children.
Gill
Brian Pottorff wrote:
Are there any good reasons why one should not change a child record's
parent by substituting CLEUNIKs that exist already?
Signaler
0
0
Brian Pottorff
#3
Posté le 20 juin 2001 - 11:46
Hi, GP:
I'm not in need of this strategy at the moment - but it makes sense to
me as an option. I used to do this with binary trees in C in the old
days. Substituting pointers made it easy to move whole subtrees with one
line of code.
In Windev, so long as one is only substituting keys that already exist
and not making up new ones that could conflict with the automatic key
assignment of the language, why not?
Signaler
0
0
GP
#4
Posté le 20 juin 2001 - 15:59
No Brian,
that doesnt make any sense. Either you have to rethink your concept or to
use ordinary long integers as a key. The cleuniks make a lot of sense in
regards to .. f.i.
customer wants to change the customer number at any time, but the cust# is
in a lot of records. Use a cleunik for customer records instead and just
"show" the customer number. Now they can change their customer numbers as
often as they want, they´ll be unable to disturb the program.
"Brian Pottorff" <pi@zianet.com> schrieb im Newsbeitrag
news:3b2fcc4e@news....
Are there any good reasons why one should not change a child record's
parent by substituting CLEUNIKs that exist already?
Signaler
0
0
GP
#5
Posté le 20 juin 2001 - 20:53
You´re right (last paragraph). To avoid any unwanted interference with the
automatic key generation for the cleunik, just create your own long int key.
Just a thought.
Günter Predl (Sorry, didnt know about the "GP" before posting and cant
change it now)
"Brian Pottorff" <pi@zianet.com> schrieb im Newsbeitrag
news:3B30C557.A9C21C24@zianet.com...
Hi, GP:
I'm not in need of this strategy at the moment - but it makes sense to
me as an option. I used to do this with binary trees in C in the old
days. Substituting pointers made it easy to move whole subtrees with one
line of code.
In Windev, so long as one is only substituting keys that already exist
and not making up new ones that could conflict with the automatic key
assignment of the language, why not?
Signaler
0
0
→ Revenir à WINDEV 2024
WINDEV 2024
WEBDEV 2024
WINDEV Mobile 2024
WINDEV (précédentes versions)
Français
English
Español
Portuguesa
Fermer cette fenêtre
Type de recherche
Uniquement les sujets
Tous les messages
Période de recherche
Date indifférente
Moins d'une heure
Moins de 24 heures
Moins d'une semaine
Moins d'un mois
Moins d'un an
Annuler
Aperçu de votre message
Ajouter une image
Importer une image depuis une URL
Envoyer une image depuis un fichier de votre disque
Déposez ici un fichier ou cliquez sur "Parcourir..."
ou
Annuler
0%
WLangage
SQL
XML, HTML
JAVA, Javascript
Texte