Re: Field name-subcategory
This WebDNA talk-list message is from 1997
It keeps the original formatting.
numero = 12744
interpreted = N
texte = >>>> Just a note, I tried to use a field named subcategory. I would get >>>> unpredictable results and errors, when I switched the field name to >>>> kategory everything was a-ok. I really didn't have time to investigate >>>> the issue as renaming the field was a quick and easy solution for this >>>> client. >>>> >>>> Any ideas as to why subcategory would be a problem?>>> Did you have other fields named something like category? Perhaps it was >>> getting confused with a fieldname that was a portion of another fieldname. >>> I believe we have fixed this for the next minor release.>>You bet I had category and subcategory>Several months ago I ran into that same problem. You can not have field >names that are subsets of other field names. ie: color and color1 or >description and shortdescription. What the heck is going on here?How long have people known about this problem and NOT posted the problem or the solution to this list? Has this really been a problem for months, as the previous message claims? Did PCS just learn about this recently? If this problem has been known for several months by PCS, why is it NOT mentioned in the docs or anywhere else?Thank you to the conscientious person who finally posted this problem on WebDNA-Talk. It's about time someone reported the problem, especially since others have apparently known about it for months but never mentioned it to the rest of us.Come on, guys! People are creating entire new businesses around this software, and bugs like this one - mixing up the fields because some field names are similar (instead of identical) is a very serious deal!One of the most critical functional requirements of any database software is the ablity to identify every field by it's unique name. When a database software doesn't even see its own field names as unique, that's a very serious technical problem that should be posted immediately, not kept a secret for months - especially when the solution is as simple as changing a single letter in the name ...PLEASE ... to anyone who discovers a new WebCat2 problem and learns of the solution to that problem ... please do NOT keep your problems and solutions a secret from the rest of us. We can all help each other if we ALL post our problems and solutions to this list. Waiting for someone else to mention a problem you solved months ago doesn't do us the rest of us any good, and it doesn't do PCS any good either.How can PCS fix something they don't know about? Please, tell them your bug discoveries immediately!Maybe I just got up on the wrong side of the bed this morning, or maybe I'm out of line, so I apologize if this message is improper. But it really bothers me that this problem may have been around for months already, yet no one bothered to post any messages about it until now.Now I have to worry and wonder just how many OTHER problems like this are lurking under the surface of WebCat2, waiting to make me look like a fool when a potential customer discovers yet another unreported/undocumented bug ... a bug that some other WebCat2 user (or PCS) has known about for months but never bothered to report ... a bug I could have dealt with in less than 5 minutes if only someone would have told me about it when they first discovered it.Needless to say, I'm not having a very good day now ... so I hope everyone else can make up for it by NOT sharing my disappointment and frustration ... :-(Sincerely, Ken Grome WebDNA Solutions http://www.hui.net/dna/webdna.html.
Associated Messages, from the most recent to the oldest:
>>>> Just a note, I tried to use a field named subcategory. I would get >>>> unpredictable results and errors, when I switched the field name to >>>> kategory everything was a-ok. I really didn't have time to investigate >>>> the issue as renaming the field was a quick and easy solution for this >>>> client. >>>> >>>> Any ideas as to why subcategory would be a problem?>>> Did you have other fields named something like category? Perhaps it was >>> getting confused with a fieldname that was a portion of another fieldname. >>> I believe we have fixed this for the next minor release.>>You bet I had category and subcategory>Several months ago I ran into that same problem. You can not have field >names that are subsets of other field names. ie: color and color1 or >description and shortdescription. What the heck is going on here?How long have people known about this problem and NOT posted the problem or the solution to this list? Has this really been a problem for months, as the previous message claims? Did PCS just learn about this recently? If this problem has been known for several months by PCS, why is it NOT mentioned in the docs or anywhere else?Thank you to the conscientious person who finally posted this problem on WebDNA-Talk. It's about time someone reported the problem, especially since others have apparently known about it for months but never mentioned it to the rest of us.Come on, guys! People are creating entire new businesses around this software, and bugs like this one - mixing up the fields because some field names are similar (instead of identical) is a very serious deal!One of the most critical functional requirements of any database software is the ablity to identify every field by it's unique name. When a database software doesn't even see its own field names as unique, that's a very serious technical problem that should be posted immediately, not kept a secret for months - especially when the solution is as simple as changing a single letter in the name ...PLEASE ... to anyone who discovers a new WebCat2 problem and learns of the solution to that problem ... please do NOT keep your problems and solutions a secret from the rest of us. We can all help each other if we ALL post our problems and solutions to this list. Waiting for someone else to mention a problem you solved months ago doesn't do us the rest of us any good, and it doesn't do PCS any good either.How can PCS fix something they don't know about? Please, tell them your bug discoveries immediately!Maybe I just got up on the wrong side of the bed this morning, or maybe I'm out of line, so I apologize if this message is improper. But it really bothers me that this problem may have been around for months already, yet no one bothered to post any messages about it until now.Now I have to worry and wonder just how many OTHER problems like this are lurking under the surface of WebCat2, waiting to make me look like a fool when a potential customer discovers yet another unreported/undocumented bug ... a bug that some other WebCat2 user (or PCS) has known about for months but never bothered to report ... a bug I could have dealt with in less than 5 minutes if only someone would have told me about it when they first discovered it.Needless to say, I'm not having a very good day now ... so I hope everyone else can make up for it by NOT sharing my disappointment and frustration ... :-(Sincerely, Ken Grome WebDNA Solutions http://www.hui.net/dna/webdna.html.
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:
[ShowIf] and empty fields (1997)
Protect vs Authenicate (1997)
FM PRO Compatibility Issue - Single Database w/o Conversions (1997)
Limiting user access to .tmpl files (1997)
[WebDNA] Check to see if certain characters are numeric? (2016)
Emailer & WebStar Mail and 551 Error (2000)
Setting up shop (1997)
newbie Q: [cart] documentation (1999)
database size? (1997)
PCS Frames (1997)
WebMerchant and MacAuthorize Errors (1998)
Windows 95/NT tip of the month (1998)
[countwords] (2002)
Bug when including a db file ... ? (2000)
Duplicate Messages (1998)
Help formatting search results w/ table (1997)
Limit to Field Length in DB (1998)
can anyone confirm this behavior? (2003)
read and write you own cookies with webcat (1997)
Commas in search (1998)