Re: OK to delete records while finding them?
This WebDNA talk-list message is from 2000
It keeps the original formatting.
numero = 32479
interpreted = N
texte = >Is there some inherent danger in deleting a record from a db within >a [founditems] loop which is finding >records in that same db?Yes, this is bad. When you do a [SEARCH], webcat creates an internal list of record numbers. It then uses that list to call up the info from the correct lines. If you do a [DELETE], the internal list stays the same, but the info that's really in the database is wrong.For example, let's say your search returns the first, second, and third records in a database:Sku 1 2 3After the first [DELETE], your db might look like thisSKU 2 3So on the next iteration, webcat will look at the second line. Instead of finding the record with SKU=2, it will find the record with SKU=3. Since it doesn't know you don't want that, bad things happen.A simple solution is to replace a field with a unique phrase/word and then delete all those records after the [FOUNDITEMS] loop is complete (this will preserve the line numbering):[SEARCH db=some.db&neSKUdatarq=[SKU]] [FOUNDITEMS] [REPLACE db=some.db&eqSKUdatarq=[SKU]]SKU=DELETEME[/REpLACE] [/FOUNDITEMS] [/SEARCH] [DELETE db=some.dn&eqSKUdatarq=DELETEME]Michael------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list
. To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/
Associated Messages, from the most recent to the oldest:
>Is there some inherent danger in deleting a record from a db within >a [founditems] loop which is finding >records in that same db?Yes, this is bad. When you do a [search], webcat creates an internal list of record numbers. It then uses that list to call up the info from the correct lines. If you do a [delete], the internal list stays the same, but the info that's really in the database is wrong.For example, let's say your search returns the first, second, and third records in a database:Sku 1 2 3After the first [delete], your db might look like thisSKU 2 3So on the next iteration, webcat will look at the second line. Instead of finding the record with SKU=2, it will find the record with SKU=3. Since it doesn't know you don't want that, bad things happen.A simple solution is to replace a field with a unique phrase/word and then delete all those records after the [founditems] loop is complete (this will preserve the line numbering):[SEARCH db=some.db&neSKUdatarq=[SKU]] [founditems] [REPLACE db=some.db&eqSKUdatarq=[SKU]]SKU=DELETEME[/REpLACE] [/FOUNDITEMS] [/SEARCH] [DELETE db=some.dn&eqSKUdatarq=DELETEME]Michael------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/
Michael Winston
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:
Math function in Formula.db (1997)
[WebDNA] Setting up a new server, hierarchy question (2014)
Errata: WCS Newbie question (1997)
How far do [showif]s go? (1997)
Different Tax levels (1998)
Does webcatalog recognise NULL values? (1998)
session handling (2004)
SERIAL NUMBER PROBLEM *AGAIN*!!! (1998)
Problems passing [SKU] with $Replace in 2.0 (1997)
Great product and great job ! (1997)
PIXO support (1997)
Error: Permision deny. (2005)
[WebDNA] Processor Maxing out (2010)
[SMSI] WebDNA is too good to go away! (2006)
Searching with a form (2000)
price totals (2003)
unsubscribe (1997)
Problems with webcat 2.01 for NT (1997)
redirect with frames (1997)
OT: Where to turn (2003)