Re: WebDNA deletes major DB data big time
This WebDNA talk-list message is from 2004
It keeps the original formatting.
numero = 55776
interpreted = N
texte = Oh yes, believe me I'm quite versed in the usage of [url] and when they are needed and when they are not.My specific issue was that I had about 20 lines of code with a delete routine. It was working fine and the customer asked me to change something, and they gave me a deadline of December 23rd. Some of the code looked like this:eqMFRSKUdatarq=[sku]&eqSHOWSKUdatarq=[show_sku]and some of the code looked like this:eqJLRSKUdatarq=[sku]&eqSHOWSKUdatarq=[show_sku]Through a series of showif/hideif routines either the JLR or MFR code was being selected. Like I said, it worked until they wanted me to change it. Of course it was a stupid mistake that I made, but it was very difficult to find where the problem was, or more accurately when and why it was happening since it was a run time error and not bad code.The real issue here is that, right after the deadline was assigned I had a death in my family (the 4th death in 5 months I might add) and I was unable to take even 1 day off from work because the deadline was right before Christmas and the customer was closing for 2 weeks after that.So I accepted the blame for the problem and reminded the customer that they did not permit any leeway for my bereavement, especially having a loss so close to a big holiday. They've not complained since then, they've not brought up the topic, and were even a little embarrassed when I said my company would recover the data for them.But to continue with this thread, I was thinking that issues like this data loss could also be caused by code like this:delete db=database.db&eq[var]datarq=[value]and then the wrong var/value pair is passed. In my specific case, since I had the MFR/JLR routines backwards that part of the criteria was ignored and it simply deleted everything that matched the SHOWSKU=[show_sku].So that's it. Do I blame my uncle for passing away 3 days before Christmas? Or do I blame my customer for saying "We're sorry but we still need this done before our winter break." If I recall I didn't get any sleep that week because of family issues, holiday issues and work issues.Matthew Perosinj-singles.comijo.comGary Krockover wrote:> I would think that you would want that to be a "required" field as well;> eqskudataRQ=[url][sku][/url]>> Also, if a SKU is a number or otherwise does not possibly have any > characters other than A-Z/0-9, is the url'ing really required or is it > more of good coding habit?>> Oh, and in Matt's defense, I think that was just a quick example from > him....>> :)>> GK>>>>>> Hi Matthew,>> I can relate with you in "learning the hard way".>>>> The above needs to have URLS in it: eqRSKUdata=[url][sku][/url]>> if there is any spaces or non-html characters.>>>> Donovan>>>>>>>> -- >> =o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o>> DONOVAN D. BROOKE Eucalyptus Design>> <-Web Development (specializing in eCommerce), ->>> <-Graphic Design, and Pre-Press Consultation ->>>>> ADDRESS:> Donovan Brooke>> DBA Eucalyptus Design>> N2862 Summerville Park Rd.>> Lodi, WI 53555>> PH:> 1.608.592.3567>> Web:> http://www.euca.us>> =o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o>>>>>> ------------------------------------------------------------->> 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://webdna.smithmicro.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://webdna.smithmicro.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://webdna.smithmicro.com/
Associated Messages, from the most recent to the oldest:
Oh yes, believe me I'm quite versed in the usage of [url] and when they are needed and when they are not.My specific issue was that I had about 20 lines of code with a delete routine. It was working fine and the customer asked me to change something, and they gave me a deadline of December 23rd. Some of the code looked like this:eqMFRSKUdatarq=[sku]&eqSHOWSKUdatarq=[show_sku]and some of the code looked like this:eqJLRSKUdatarq=[sku]&eqSHOWSKUdatarq=[show_sku]Through a series of showif/hideif routines either the JLR or MFR code was being selected. Like I said, it worked until they wanted me to change it. Of course it was a stupid mistake that I made, but it was very difficult to find where the problem was, or more accurately when and why it was happening since it was a run time error and not bad code.The real issue here is that, right after the deadline was assigned I had a death in my family (the 4th death in 5 months I might add) and I was unable to take even 1 day off from work because the deadline was right before Christmas and the customer was closing for 2 weeks after that.So I accepted the blame for the problem and reminded the customer that they did not permit any leeway for my bereavement, especially having a loss so close to a big holiday. They've not complained since then, they've not brought up the topic, and were even a little embarrassed when I said my company would recover the data for them.But to continue with this thread, I was thinking that issues like this data loss could also be caused by code like this:delete db=database.db&eq[var]datarq=[value]and then the wrong var/value pair is passed. In my specific case, since I had the MFR/JLR routines backwards that part of the criteria was ignored and it simply deleted everything that matched the SHOWSKU=[show_sku].So that's it. Do I blame my uncle for passing away 3 days before Christmas? Or do I blame my customer for saying "We're sorry but we still need this done before our winter break." If I recall I didn't get any sleep that week because of family issues, holiday issues and work issues.Matthew Perosinj-singles.comijo.comGary Krockover wrote:> I would think that you would want that to be a "required" field as well;> eqskudataRQ=[url][sku][/url]>> Also, if a SKU is a number or otherwise does not possibly have any > characters other than A-Z/0-9, is the url'ing really required or is it > more of good coding habit?>> Oh, and in Matt's defense, I think that was just a quick example from > him....>> :)>> GK>>>>>> Hi Matthew,>> I can relate with you in "learning the hard way".>>>> The above needs to have URLS in it: eqRSKUdata=[url][sku][/url]>> if there is any spaces or non-html characters.>>>> Donovan>>>>>>>> -- >> =o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o>> DONOVAN D. BROOKE Eucalyptus Design>> <-Web Development (specializing in eCommerce), ->>> <-Graphic Design, and Pre-Press Consultation ->>>>> ADDRESS:> Donovan Brooke>> DBA Eucalyptus Design>> N2862 Summerville Park Rd.>> Lodi, WI 53555>> PH:> 1.608.592.3567>> Web:> http://www.euca.us>> =o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o>>>>>> ------------------------------------------------------------->> 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://webdna.smithmicro.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://webdna.smithmicro.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://webdna.smithmicro.com/
Matthew A Perosi
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:
Emailer setup (1997)
How many Databases can I open? (2003)
Developer Edition - Connection Limit (2006)
Associative lookup style? + bit more (1997)
Million product store (2003)
Multiple Passwords (1997)
WebCat templates for TyphoonPro admin (1999)
Paranoid about serial numbers...not (1998)
Comparing two fields so the match (1998)
RE: MacFinder -- a new WebDNA web site (1998)
syntax question, not in online refernce (1997)
WebCat2b13MacPlugIn - More limits on [include] (1997)
Unknown error: OrderNotCreated (1997)
Can this be done? (1997)
Database Path (1998)
[isfile] ? (1997)
Limitations on fields? Server is crashing (1997)
Error: Too many nested [xxx] contexts (1997)
Re:2nd WebCatalog2 Feature Request (1996)
Reversed words (1997)