Re: [REPLACE] inside [FOUNDITEMS]
This WebDNA talk-list message is from 1998
It keeps the original formatting.
numero = 19204
interpreted = N
texte = >>>I don't believe that [replace] will change the [index] values (the >>>positions of the rows in the db), just the values in the database. >> >>I believe you are correct.This is not correct. Replace *can* change the index values, I've proven it in my testing ...>For my personal feeling [Replace] seems to be save when you have a >unique ID and use just this value as main parameter for [Replace].Yes, that's what I said earlier, but this only works if you do *not* use the replace context to change the unique ID -- and you must also be careful that any other fields you are changing do *not* appear in the search parameters. If either one of these situations occurs, it is possible for WebCat to change the wrong records, because the index values will probably change ...>Every programmer develops his personal style over time. For me, I never >ever give my program the chance to replace more than one record or delete >records from the same selection where I'm in at the moment.Neither [delete] nor [replace] will do what you're trying to avoid -- unless you use them INSIDE a founditems context -- so you're safe if you ONLY use replace and delete on their own, and never inside a founditems loop.Sincerely, Ken Grome 808-737-6499 WebDNA Solutions mailto:ken@webdna.net http://www.webdna.net
Associated Messages, from the most recent to the oldest:
>>>I don't believe that
[replace] will change the [index] values (the >>>positions of the rows in the db), just the values in the database. >> >>I believe you are correct.This is not correct. Replace *can* change the index values, I've proven it in my testing ...>For my personal feeling
[replace] seems to be save when you have a >unique ID and use just this value as main parameter for
[replace].Yes, that's what I said earlier, but this only works if you do *not* use the replace context to change the unique ID -- and you must also be careful that any other fields you are changing do *not* appear in the search parameters. If either one of these situations occurs, it is possible for WebCat to change the wrong records, because the index values will probably change ...>Every programmer develops his personal style over time. For me, I never >ever give my program the chance to replace more than one record or delete >records from the same selection where I'm in at the moment.Neither
[delete] nor
[replace] will do what you're trying to avoid -- unless you use them INSIDE a founditems context -- so you're safe if you ONLY use replace and delete on their own, and never inside a founditems loop.Sincerely, Ken Grome 808-737-6499 WebDNA Solutions mailto:ken@webdna.net http://www.webdna.net
Kenneth Grome
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
Associative lookup style? + bit more (1997)
New Install (2003)
Caching [include] files ... (1997)
[OT] What log analyzer do you use? (2000)
WCS Newbie question (1997)
Variable security (2000)
Problem with Formulas.db (1998)
WebCatalog can't find database (1997)
WC2b15 File Corruption (1997)
Calculating multiple shipping... (1997)
Case statement (2003)
NTbeta18 corrupted? (1997)
quantity minimum problem (1997)
Re:Can anyone help me with this shipping thing? (1998)
Pithy questions on webcommerce & siteedit (1997)
popups, netscape vs explorer (1997)
Emailer (1998)
RE: Shopping Cart Questions (1998)
[WebDNA] Cannot get WebDNA and MySQL working. (2015)
WebCatalog complains that the service is not running. (1998)