Re: I think I found a bug
This WebDNA talk-list message is from 2001
It keeps the original formatting.
numero = 37070
interpreted = N
texte = Curiosity got the best of me and I played with this a bit...It looks like the max= parameter works the same in [replace] as it does in [search] -- if the max= value is not a positive integer, the parameter is ignored, resulting in all found records being listed / replaced.I would not call this a bug, just an unspecified behavior resulting from providing an out-of-range value for a parameter.- BrianAt 4:54 PM 7/9/2001, Arturo Vargas wrote:>Reading the docs I was given the impression that [replace] had the same>parameters as [search]>>and this is correct for instance I have been using successfully the max>parameter with replace. But recently some one entered 0 as the max parameter>in this [replace] and every single entry was replaced. as if the max>parameter wasn't there. I wonder if there is some kind of reason for the>number 0 to not work with the max parameter. Does any body know if this is a>bug of webcat or is there a reason for max=0 to not work.>>Arturo Vargas-- <= Brian C. Fries, BrainScan Software http://www.brainscansoftware.com =>-------------------------------------------------------------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:
Curiosity got the best of me and I played with this a bit...It looks like the max= parameter works the same in [replace] as it does in [search] -- if the max= value is not a positive integer, the parameter is ignored, resulting in all found records being listed / replaced.I would not call this a bug, just an unspecified behavior resulting from providing an out-of-range value for a parameter.- BrianAt 4:54 PM 7/9/2001, Arturo Vargas wrote:>Reading the docs I was given the impression that [replace] had the same>parameters as [search]>>and this is correct for instance I have been using successfully the max>parameter with replace. But recently some one entered 0 as the max parameter>in this [replace] and every single entry was replaced. as if the max>parameter wasn't there. I wonder if there is some kind of reason for the>number 0 to not work with the max parameter. Does any body know if this is a>bug of webcat or is there a reason for max=0 to not work.>>Arturo Vargas-- <= Brian C. Fries, BrainScan Software http://www.brainscansoftware.com =>-------------------------------------------------------------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/
Brian Fries
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:
'does not contain' operator needed ... (1997)
Bug report: Insecure variables and SPAWN (2001)
JS version of this (2007)
[BULK] [WebDNA] why append made record twice in database (2012)
WebCatalog for guestbook ? (1997)
database paths/names, and a typo (1997)
Thanks ! (1997)
How to append text after the sign & (1997)
Fields font size (2003)
WC Bulletin Board Issue (2003)
FAX orders (1996)
The List is Changing (1997)
Large databases in WebCat (1997)
Client-side Image Maps and WebCat? (1998)
WebCat2b14MacPlugIn - [include] doesn't hide the search string (1997)
WebCat2b13MacPlugIn - [include] doesn't allow creator (1997)
[date] formatting bug inside [orderfile]? (1998)
PCS Customer submissions ? (1997)
Banners and sort of random display (1997)
database performance/design question (2000)