Failure to document significant changes ...

This WebDNA talk-list message is from

2000


It keeps the original formatting.
numero = 34029
interpreted = N
texte = >Yes, I think SM should definitely have placed a large warning to the >effect of: > > Anyone stupid enough to use embedded spaces in field names will > discover that their web sites will break, due to some updates in > the consistency of WebCatalog's parser.I've had years of database experience prior to webcat. It's not news to me that most other db programs do not allow spaces in field names. My understanding of this situation is *exactly* why I went directly to Grant years ago and asked him about this apparent discrepancy in webcatalog. After all, Grant wrote the webcatalog software program, so I expected to get the facts from him -- and I did:Grant *specifically* told me that he coded webcatalog to deal with spaces in field names as if those spaces were no different from alphanumeric characters. In fact, he said I could use spaces in my field names with no problem -- regardless of the limitations of *other* database program.He said webcat was based on a text-parsing model, and a space character was no different to webcatalog than any other character in a field name. And guess what? He was right! He gave me the facts, and those facts have been true for 4 years already. We have *always* been able to use spaces in webcat field names -- until now.This is not an issue of who has the most knowledge of other database software, or what kinds of 'conventions' are used in those other database programs. This is a clear issue of SM's failure to document a *significant* change that can make their software incompatible with previous webdna sites.It is irresponsible of SM to fail to document something like this.They made a special effort to change the parser in order to ELIMINATE the space character -- so it would be XML-compliant. That's great, but why then did they fail to tell us about it themselves, in writing in the docs where it belongs, before releasing it?I really don't care whether or not they get rid of the space character and the letters a-g and any other formerly-valid field/parameter name characters, AS LONG AS THEY TELL US ABOUT IT IN ADVANCE SO WE DO NOT EXPERIENCE PROBLEMS AFTER UPGRADING. ================================ Kenneth Grome, WebDNA Consultant 808-737-6499 http://webdna.net ================================------------------------------------------------------------- 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: Failure to document significant changes ... (Kim Ingram 2000)
  2. Re: Failure to document significant changes ... (Kenneth Grome 2000)
  3. Re: Failure to document significant changes ... (John Peacock 2000)
  4. Failure to document significant changes ... (Kenneth Grome 2000)
>Yes, I think SM should definitely have placed a large warning to the >effect of: > > Anyone stupid enough to use embedded spaces in field names will > discover that their web sites will break, due to some updates in > the consistency of WebCatalog's parser.I've had years of database experience prior to webcat. It's not news to me that most other db programs do not allow spaces in field names. My understanding of this situation is *exactly* why I went directly to Grant years ago and asked him about this apparent discrepancy in webcatalog. After all, Grant wrote the webcatalog software program, so I expected to get the facts from him -- and I did:Grant *specifically* told me that he coded webcatalog to deal with spaces in field names as if those spaces were no different from alphanumeric characters. In fact, he said I could use spaces in my field names with no problem -- regardless of the limitations of *other* database program.He said webcat was based on a text-parsing model, and a space character was no different to webcatalog than any other character in a field name. And guess what? He was right! He gave me the facts, and those facts have been true for 4 years already. We have *always* been able to use spaces in webcat field names -- until now.This is not an issue of who has the most knowledge of other database software, or what kinds of 'conventions' are used in those other database programs. This is a clear issue of SM's failure to document a *significant* change that can make their software incompatible with previous webdna sites.It is irresponsible of SM to fail to document something like this.They made a special effort to change the parser in order to ELIMINATE the space character -- so it would be XML-compliant. That's great, but why then did they fail to tell us about it themselves, in writing in the docs where it belongs, before releasing it?I really don't care whether or not they get rid of the space character and the letters a-g and any other formerly-valid field/parameter name characters, AS LONG AS THEY TELL US ABOUT IT IN ADVANCE SO WE DO NOT EXPERIENCE PROBLEMS AFTER UPGRADING. ================================ Kenneth Grome, WebDNA Consultant 808-737-6499 http://webdna.net ================================------------------------------------------------------------- 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/ Kenneth Grome

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:

quantity minimum problem (1997) [founditems][replacefounditems] (2003) Bad spawn! Finish your work! (2002) PIXO support (1997) Security Tip (1996) how to get s repeatedly in and out of a form? (1999) Help! WebCat2 bug (1997) Grep Question - SOLVED (2003) [shownext max=?] armed (1997) SQL Error 22003 : Found the workaround (2001) Problems appending to database (1997) Search design (1997) [WebDNA] Cannot read LongText data type from MySQL (2011) File Upload (1997) cart (1997) [OT] mozilla / Seamonkey (2007) Where's Cart Created ? (1997) RE:DatabaseHelper (1997) Interesting speed comparison .. (2003) Major Security Hole (1998)