Re: [REPLACE] inside [FOUNDITEMS]
This WebDNA talk-list message is from 1998
It keeps the original formatting.
numero = 19202
interpreted = N
texte = At 14:29 Uhr 29.07.1998, PCS Technical Support wrote:>>Maybe Grant can clarify this, but 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. Which means [replace] would be safe, but >perhaps confusing if the side-effect of the replace is that the record no >longer matches the original search criteria, yet it still appears in the >list of found items. Hm. I got confused while watching this thread... I don't think we can see [Replace] generally as a lookup. A lookup looks for the first field which matches the request, but [Replace] is supposed to change a lot of records at once. Fine thing, but what if you do a replace for a certain record while in [founditems] and it actually changes five other records which are probably already processed? 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]. But - personal feeling again - I won't rely on that... 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. And I won't start a new search within the same selection, unless the software has commands like push on stack to secure the current record (or the ability to save selections).However, a possibility to change fields of the current record would make this whole discussion obsolete - isn't that a daily job for such an application? Any database can go to one record, change some values and save the record. WebCat can do this in a cart, but not in a database - why?I don't ask for something complicated, just for something like that: [SetField field=DESCRIPTION&value=good stuff] which changes one field of the current record... Peter__________________________________________ Peter Ostry - po@ostry.com - www.ostry.com Ostry & Partner - Ostry Internet Solutions Auhofstrasse 29 A-1130 Vienna Austria fon ++43-1-8777454 fax ++43-1-8777454-21
Associated Messages, from the most recent to the oldest:
At 14:29 Uhr 29.07.1998, PCS Technical Support wrote:>>Maybe Grant can clarify this, but 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. Which means
[replace] would be safe, but >perhaps confusing if the side-effect of the replace is that the record no >longer matches the original search criteria, yet it still appears in the >list of found items. Hm. I got confused while watching this thread... I don't think we can see
[replace] generally as a lookup. A lookup looks for the first field which matches the request, but
[replace] is supposed to change a lot of records at once. Fine thing, but what if you do a replace for a certain record while in
[founditems] and it actually changes five other records which are probably already processed? 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]. But - personal feeling again - I won't rely on that... 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. And I won't start a new search within the same selection, unless the software has commands like push on stack to secure the current record (or the ability to save selections).However, a possibility to change fields of the current record would make this whole discussion obsolete - isn't that a daily job for such an application? Any database can go to one record, change some values and save the record. WebCat can do this in a cart, but not in a database - why?I don't ask for something complicated, just for something like that: [SetField field=DESCRIPTION&value=good stuff] which changes one field of the current record... Peter__________________________________________ Peter Ostry - po@ostry.com - www.ostry.com Ostry & Partner - Ostry Internet Solutions Auhofstrasse 29 A-1130 Vienna Austria fon ++43-1-8777454 fax ++43-1-8777454-21
Peter Ostry
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:
combine search (1998)
Date Formats (1997)
Fw: error message (2000)
Setting up the server (1997)
Quit revisited (1997)
tmpl Vs DB (1999)
ShowNext truncating passed variable?? (1997)
Doing VALIDCARD right? (1998)
Replace Statement (1997)
serial number generation (1997)
Retaining data (2003)
A Global Variable (1997)
Showing once on a founditems (1997)
Bugs in IE 6.0 ? (2003)
Viewing old carts (was FEW QUESTIONS) (1997)
I'm new be kind (1997)
[ShowNext] (1997)
Re:no template caching (1997)
Emails sent twice (2000)
RE: Multiple Stores and WebCatalog Prefs (1997)