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:
test (2002)
WebCatalog/Mac 2.1b2 New Features (1997)
Generating unique SKU from [cart] (1997)
Email notification to one of multiple vendors ? (1997)
Problem (1997)
[SHOWIF]s and empty arguments (1997)
Multiple prices per product (2004)
[WebDNA] New Server Setup (2016)
Buying sans cart (1997)
WCS Newbie question (1997)
[WebDNA] Secure cookies (HttpOnly/Secure) (2013)
There's a bug in the math context ... (1997)
serial number dishing (1997)
CloseDataBase vs CommitDataBase (2007)
[WebDNA] Mac OS Intel version? (2008)
Menu to select product variations (1997)
random within a specified range (2001)
Location of Webcat site in folder hierarchy (1997)
Test (2003)
WebCatalog (1998)