db caching in bizarre ways

This WebDNA talk-list message is from

2001


It keeps the original formatting.
numero = 37376
interpreted = N
texte = I went from WebCat 2.6 to 4.0.2rc1 last month. After beating my head against the wall with several WebStar crashes a day for 6 weeks, I gave up on 4 and am now running (almost) solid with 3.0.7. But a new problem has cropped up.I have admin pages where I can tweak a user's account, most notably, change his status from 'current' to 'expired' (using my own db, not the built-in users.db). After switching to ver 3 last night, my admin edits are being written to disk, but seemingly not to RAM. Unless I search anew explicitly for one record. I'm certainly confused. When I do a search to collect all the records that expire today, I get three members. I change them to expired, and a check to the db file on disk shows them changed. But when I again search for expired members, they show up again, and the edit pages for the individuals also show their previous 'current' status. However, when I hit reload on either of those pages, I get the correct, updated 'expired' status. So it seems to be a browser caching issue. However, what does that have to do with WebCat, and why would ver 2 and ver 4 work, but ver 3 not? The WebCat 'Show Databases' page does not show the updated number of records after adding or deleting records either.I have checked to see if I refer to the db in two different ways (per some discussion in the archives), but it is always referred to as relative (in the same folder as the templates).There's also something funny going on with carts hanging around in my browser cache. command=Newcart doesn't make a new one, nor does specifying [cart] in the template, when none was passed, make a new one. Hitting Reload does kick in a new cart. God what a mess.This is a major problem in administering my members. Is there a hidden setting that I can make to fix this bad behavior?Thanks, Terry Wilson terry@terryfic.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: db caching in bizarre ways (Jesse Proudman (Lists Account) 2001)
  2. Re: db caching in bizarre ways (John Peacock 2001)
  3. Re: db caching in bizarre ways (Glenn Busbin 2001)
  4. db caching in bizarre ways (Terry Wilson 2001)
I went from WebCat 2.6 to 4.0.2rc1 last month. After beating my head against the wall with several WebStar crashes a day for 6 weeks, I gave up on 4 and am now running (almost) solid with 3.0.7. But a new problem has cropped up.I have admin pages where I can tweak a user's account, most notably, change his status from 'current' to 'expired' (using my own db, not the built-in users.db). After switching to ver 3 last night, my admin edits are being written to disk, but seemingly not to RAM. Unless I search anew explicitly for one record. I'm certainly confused. When I do a search to collect all the records that expire today, I get three members. I change them to expired, and a check to the db file on disk shows them changed. But when I again search for expired members, they show up again, and the edit pages for the individuals also show their previous 'current' status. However, when I hit reload on either of those pages, I get the correct, updated 'expired' status. So it seems to be a browser caching issue. However, what does that have to do with WebCat, and why would ver 2 and ver 4 work, but ver 3 not? The WebCat 'Show Databases' page does not show the updated number of records after adding or deleting records either.I have checked to see if I refer to the db in two different ways (per some discussion in the archives), but it is always referred to as relative (in the same folder as the templates).There's also something funny going on with carts hanging around in my browser cache. command=Newcart doesn't make a new one, nor does specifying [cart] in the template, when none was passed, make a new one. Hitting Reload does kick in a new cart. God what a mess.This is a major problem in administering my members. Is there a hidden setting that I can make to fix this bad behavior?Thanks, Terry Wilson terry@terryfic.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/ Terry Wilson

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:

Unencrypt Password (2004) Re:Email Problem (1997) Re:upgrade problem with users.db (1998) ftp access on Macos X (2000) [if] (2003) Quitting WebMerchant ? (1997) [WebDNA] [sendmail] random duplicates (2010) [cart] not being interpreted inside [founditems] (1997) database visibility (2000) Re:2nd WebCatalog2 Feature Request (1996) Part Html part WebDNA (1997) Emailer port change (1997) Nested Loops and SHOWIFs (1997) ALL CAPS converted to All Caps - first letter capitalized only (2002) How true is this? (1999) Validating a date (2000) How to Display text in empty fields (1997) Date Range search (1997) multi-paragraph fields (1997) Multiple Pulldowns (1997)