Re: Every other record deleted

This WebDNA talk-list message is from

2005


It keeps the original formatting.
numero = 63661
interpreted = N
texte = On Thu, 22 Dec 2005 10:49:29 -0600 Donovan Brooke wrote: > Well, I didn't see anything from first glance that would delete > every other record exactly. Thanks for the extra set of eyes > > A couple of comments.. > > Your use of [URL][/URL] should be increased greatly, unless you > have very maticulous form variable checks. If someone puts an > "&" or "=" in the zip (for example), it will mess with your editing context. > There are other examples as well... but URL'ing just about every > value in an append will eliminate those problems. I didn't [url] the inputs that I 'control' i.e. the zipcode is entered via a drop-down, etc. Actual form here: http://www.searchboise.com/login.html I'll keep looking though, because this is on the top of my mind as a potential culprit... > > I don't know exactly what you mean by "shared server" but if > there is a chance that database could be hit by more than one > user at the same time, you may want to put the [exclusivelock db=..] > context to work. I do this in any sensitive database. Shared server = other websites (my own & other developers) sites all hosted at once. Theoretically, all sites are protected from one another via sandboxes, but as for users hitting my ..dbs simultaneously, yes that is highly probable. > > Lastly, if you are on apache, I would make use of the global > search shell command (not sure what the best one would be) > and look for any file that contains the > phrase "listings_UNAPPROVED.db" to see if there is a stray > file somewhere that could have caused the "every other issue". I am on apache, but that's where things get over my head and I honestly don't know what access I do/don't have regarding apache. My server admin typically handles apache issues. I'll look into this a little more. Thanks again for your help. -Dan ------------------------------------------------------------- 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:

    
  1. Re: Every other record deleted ( Donovan Brooke 2005)
  2. Re: Every other record deleted ( Peter Ostry 2005)
  3. Re: Every other record deleted ( Grant Hulbert 2005)
  4. Re: Every other record deleted ( Stuart Tremain 2005)
  5. Re: Every other record deleted ( Brian Fries 2005)
  6. Re: Every other record deleted ( Jesse Proudman 2005)
  7. Re: Every other record deleted ( Jesse Proudman 2005)
  8. Re: Every other record deleted ( "Dan Strong" 2005)
  9. Re: Every other record deleted ( Donovan Brooke 2005)
  10. Re: Every other record deleted ( "Dan Strong" 2005)
  11. Re: Every other record deleted ( Donovan Brooke 2005)
  12. Re: Every other record deleted ( "Dan Strong" 2005)
  13. Re: Every other record deleted ( "Eric Miller" 2005)
  14. Every other record deleted ( "Dan Strong" 2005)
On Thu, 22 Dec 2005 10:49:29 -0600 Donovan Brooke wrote: > Well, I didn't see anything from first glance that would delete > every other record exactly. Thanks for the extra set of eyes > > A couple of comments.. > > Your use of [url][/URL] should be increased greatly, unless you > have very maticulous form variable checks. If someone puts an > "&" or "=" in the zip (for example), it will mess with your editing context. > There are other examples as well... but URL'ing just about every > value in an append will eliminate those problems. I didn't [url] the inputs that I 'control' i.e. the zipcode is entered via a drop-down, etc. Actual form here: http://www.searchboise.com/login.html I'll keep looking though, because this is on the top of my mind as a potential culprit... > > I don't know exactly what you mean by "shared server" but if > there is a chance that database could be hit by more than one > user at the same time, you may want to put the [exclusivelock db=..] > context to work. I do this in any sensitive database. Shared server = other websites (my own & other developers) sites all hosted at once. Theoretically, all sites are protected from one another via sandboxes, but as for users hitting my ..dbs simultaneously, yes that is highly probable. > > Lastly, if you are on apache, I would make use of the global > search shell command (not sure what the best one would be) > and look for any file that contains the > phrase "listings_UNAPPROVED.db" to see if there is a stray > file somewhere that could have caused the "every other issue". I am on apache, but that's where things get over my head and I honestly don't know what access I do/don't have regarding apache. My server admin typically handles apache issues. I'll look into this a little more. Thanks again for your help. -Dan ------------------------------------------------------------- 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/ "Dan Strong"

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:

Search question with a lookup (3 dbs) (2004) Multiple cart additions (1997) PIXO support (1997) Follow-Up to: Removing [showif] makes a big difference in speed (1997) Interfacing WebMerchant to www.fedex.com (1997) WebDNA Solutions ... (1997) [Webcat 2]Next (1997) Template Encryption (1998) WCS Newbie question (1997) javascript newPopwin and webcat (1998) NT Manual (1997) Multiple cart additions (1997) X Server (1999) Serving images from databases (1998) Not really WebCat- (1997) Newbie Help Needed (1998) Nt's Latest? (1997) Linked lists and Recursive searching (2003) A quickie question (1997) GuestBook example (1997)