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:

    
  1. Re: [REPLACE] inside [FOUNDITEMS] (Kenneth Grome 1998)
  2. Re: [REPLACE] inside [FOUNDITEMS] (Peter Ostry 1998)
  3. Re: [REPLACE] inside [FOUNDITEMS] (Michael Winston 1998)
  4. Re: [REPLACE] inside [FOUNDITEMS] (Kenneth Grome 1998)
  5. Re: [REPLACE] inside [FOUNDITEMS] (Bob Minor 1998)
  6. Re: [REPLACE] inside [FOUNDITEMS] (PCS Technical Support 1998)
  7. Re: [REPLACE] inside [FOUNDITEMS] (Michael Winston 1998)
  8. Re: [REPLACE] inside [FOUNDITEMS] (PCS Technical Support 1998)
  9. Re: [REPLACE] inside [FOUNDITEMS] (Dave MacLeay 1998)
  10. Re: [REPLACE] inside [FOUNDITEMS] (PCS Technical Support 1998)
  11. Re: [REPLACE] inside [FOUNDITEMS] (Kenneth Grome 1998)
  12. RE: [REPLACE] inside [FOUNDITEMS] (Olin 1998)
  13. [REPLACE] inside [FOUNDITEMS] (Michael Winston 1998)
  14. Re: [REPLACE] inside [FOUNDITEMS] (Dave MacLeay 1998)
  15. RE: [REPLACE] inside [FOUNDITEMS] (Olin 1998)
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:

international time (1997) WebCat2b13MacPlugIn - [shownext method=post] ??? (1997) [OT] Mail Error code 573?? (2006) Pithy questions on webcommerce & siteedit (1997) Fuzzy on [url] context (1998) two unique banners on one page (1997) Boolean showifs? (2000) Searching multiple Databases (1997) RE: MacFinder -- a new WebDNA web site (1998) Design Help Needed (1998) Multiple Purchase (2002) Change [cart] date (2002) Erotic Sites (1997) Security Issue (1997) Combining search criteria (2000) Shopping cart now bad (1997) [searchString] (1997) Looking for WebCat developer/contractor (2000) WebCatalog can't find database (1997) Re:2nd WebCatalog2 Feature Request (1996)