Re: I think I found a bug

This WebDNA talk-list message is from

2001


It keeps the original formatting.
numero = 37072
interpreted = N
texte = Essentially, yes. If a product doesn't work as advertised, then you have a bug. If you put a peanut butter sandwich into a VCR and it doesn't play, then that is user error.That's not to say that WebCat couldn't do more error checking. There are many situations within WebCat where putting in marginally bad information can create significantly bad results, but WebDNA is a programming language and all programming languages are capable of great havoc if not used properly, or tested thoroughly when the inputs are questionable.- brianAt 12:33 PM 7/10/2001, Andrew Simpson wrote: >So a bug would be an unspecified behaviour resulting from providing a >correct and valid value as a parameter??? > >-Andrew. > >on 10/7/01 12:18 PM, Brian Fries at brainscn@psyber.com wrote: > >> 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. >> >> - Brian >> >> At 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 > > >------------------------------------------------------------- >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 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:

    
  1. Re: I think I found a bug (Brian Fries 2001)
  2. Re: I think I found a bug (Andrew Simpson 2001)
  3. Re: I think I found a bug (Brian Fries 2001)
  4. I think I found a bug (Arturo Vargas 2001)
Essentially, yes. If a product doesn't work as advertised, then you have a bug. If you put a peanut butter sandwich into a VCR and it doesn't play, then that is user error.That's not to say that WebCat couldn't do more error checking. There are many situations within WebCat where putting in marginally bad information can create significantly bad results, but WebDNA is a programming language and all programming languages are capable of great havoc if not used properly, or tested thoroughly when the inputs are questionable.- brianAt 12:33 PM 7/10/2001, Andrew Simpson wrote: >So a bug would be an unspecified behaviour resulting from providing a >correct and valid value as a parameter??? > >-Andrew. > >on 10/7/01 12:18 PM, Brian Fries at brainscn@psyber.com wrote: > >> 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. >> >> - Brian >> >> At 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 > > >------------------------------------------------------------- >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 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:

RE: WebCat cannot handle compatible search parameters? (1997) [OT] Disable/enable field (2003) Emailer (WebCat2) (1997) (slightly off) using menu and [search] (1998) Question about Webcatalog and Webstar for Mac OS X (1998) webcat serving multiple copies of same db from ram (2000) WebCatalog NT (1996) WC hosting services required (1998) SERIAL NUMBER PROBLEM *AGAIN*!!! (1998) no global [username] or [password] displayed ... (1997) [WebDNA] contents of db files disappearing including triggers.db (2019) encrypt algorythm (2002) Date search - yes or no (1997) MacAuthorize and WebMerchant (1997) mail test (1997) FAX orders (1996) Limitations on fields? Server is crashing (1997) db Translation (2002) Re:Can this be done? (1997) &max= (2003)