Re: [WebDNA] Unexpected behavior ...
This WebDNA talk-list message is from 2010
It keeps the original formatting.
numero = 105869
interpreted = N
texte = I don't know the answers to your Q's, but to get the randomly edited records, as you desire, maybe you could try: [search db=[db]&eqskudatarq=[blank]&idxsdir=ra&RandSeed=[random] [random]&max=1] [replacefounditems]sku=[cart][/replacefounditems] [/search] As far as I can tell, the docs (or source code) never suggest(ed) found records are found in a random manner. If they were, then why even the need/availability of sdir=ra&RandSeed=xxx ? -Govinda On Oct 14, 2010, at 11:48 AM, Kenneth Grome wrote: > I wrote this script to enter a [cart] value into the sku field of one > record at a time, then display the unsorted records remaining to be > processed, sorted by idx which is a field autonumbered starting at > 1001: > > [search db=[db]&eqskudatarq=[blank]&max=1] > [replacefounditems]sku=[cart][/replacefounditems] > [/search] > > [search db=[db]&eqskudatarq=[blank]&rank=off] > [founditems][idx]
[/founditems] > [/search] > > What I observed when looking at the idx values displayed by the second > search results is that records were not being processed in a random > order. Instead this is what I observed when there were 27 records in > the db: > > First all the records from 1019 to 1027 were replaced in an apparently > random manner. Then all the records from 1009 to 1018 were replaced, > randomly. Ffinally all the records from 1001 to 1008 were replaced > randomly. > > This makes me think that there's something unusual about the number 8 > as the ending digit in the idx field. > > Instead of records being replaces randomly throughout the entire set > of resulting matches as I expected, records were replaced in "subsets" > ... where each subset contained the values starting with the highest > idx value currently in the db and decreasing until an idx value ending > in "8" was encountered. > > Even though I was not forcing webdna to replace these records > randomly, I still thought they would be replaced randomly since I > didn't use any sort parameters in the first search. And they did > appear to be replaced randomly WITHIN EACH SUBSET -- but I cannot > understand why webdna behaved like this. > > Coincidentally a few days ago Olin noted an unusual occurrence related > to the number "8", and I think his discovery may be related to this > one. > > I wouldn't exactly call this a bug, but it certainly is not what I > expected, and since I've never run into this type of thing before I'm > hoping that someone can explain why webdna replaces the found items in > subsets like this, where the smallest number in the subset is 8, > before proceeding to the next subset. > > ??? ------------ Govinda govinda(DOT)webdnatalk(AT)gmail(DOT)com
Associated Messages, from the most recent to the oldest:
I don't know the answers to your Q's, but to get the randomly edited records, as you desire, maybe you could try: [search db=[db]&eqskudatarq=[blank]&idxsdir=ra&RandSeed=
[random] [random]&max=1]
[replacefounditems]sku=
[cart][/replacefounditems] [/search] As far as I can tell, the docs (or source code) never suggest(ed) found records are found in a random manner. If they were, then why even the need/availability of sdir=ra&RandSeed=xxx ? -Govinda On Oct 14, 2010, at 11:48 AM, Kenneth Grome wrote: > I wrote this script to enter a
[cart] value into the sku field of one > record at a time, then display the unsorted records remaining to be > processed, sorted by idx which is a field autonumbered starting at > 1001: > > [search db=[db]&eqskudatarq=[blank]&max=1] >
[replacefounditems]sku=
[cart][/replacefounditems] > [/search] > > [search db=[db]&eqskudatarq=[blank]&rank=off] >
[founditems][idx]
[/founditems] > [/search] > > What I observed when looking at the idx values displayed by the second > search results is that records were not being processed in a random > order. Instead this is what I observed when there were 27 records in > the db: > > First all the records from 1019 to 1027 were replaced in an apparently > random manner. Then all the records from 1009 to 1018 were replaced, > randomly. Ffinally all the records from 1001 to 1008 were replaced > randomly. > > This makes me think that there's something unusual about the number 8 > as the ending digit in the idx field. > > Instead of records being replaces randomly throughout the entire set > of resulting matches as I expected, records were replaced in "subsets" > ... where each subset contained the values starting with the highest > idx value currently in the db and decreasing until an idx value ending > in "8" was encountered. > > Even though I was not forcing webdna to replace these records > randomly, I still thought they would be replaced randomly since I > didn't use any sort parameters in the first search. And they did > appear to be replaced randomly WITHIN EACH SUBSET -- but I cannot > understand why webdna behaved like this. > > Coincidentally a few days ago Olin noted an unusual occurrence related > to the number "8", and I think his discovery may be related to this > one. > > I wouldn't exactly call this a bug, but it certainly is not what I > expected, and since I've never run into this type of thing before I'm > hoping that someone can explain why webdna replaces the found items in > subsets like this, where the smallest number in the subset is 8, > before proceeding to the next subset. > > ??? ------------ Govinda govinda(DOT)webdnatalk(AT)gmail(DOT)com
Govinda
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:
Need correct syntax for writing to header2 (1999)
Formating found categories (1997)
Banners (1997)
Another new bug found ... (2000)
Suffix Mapping????? (1998)
[SHOWIF AND/OR] (1997)
JavaScript (1998)
[shownext] and sort (1998)
[OT] See Flash? (2003)
Re:need help please (1997)
Forbidden CGI Error (1997)
Problems with ErrorLog on Linux (2000)
JavaScript form question (2001)
RE: groups and [ShowNext] (1997)
ups quickcost [repost] (1999)
Nested tags count question (1997)
Date Calulation (1997)
$Append for Users outside the ADMIN group (1997)
WebCat2 several catalogs? (1997)
Comments in db? (1997)