Re: db caching in bizarre ways

This WebDNA talk-list message is from

2001

It keeps the original formatting. numero = 37378
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.What platform? What OS?>>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.Close the db so that its contents are cleared from memory. When it's opened again, it will write the new info to RAM.>>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.Huh? Maybe if you show your code, someone will see what's wrong.>>This is a major problem in administering my members. Is there a hidden setting that I can make to fix this bad behavior?>You're describing a lotta problems here. Take one at a time and get help solving it before working on the next.Glenn-------------------------------------------------------------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:

Re: db caching in bizarre ways (Jesse Proudman (Lists Account) 2001)
Re: db caching in bizarre ways (John Peacock 2001)
Re: db caching in bizarre ways (Glenn Busbin 2001)
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.What platform? What OS?>>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.Close the db so that its contents are cleared from memory. When it's opened again, it will write the new info to RAM.>>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.Huh? Maybe if you show your code, someone will see what's wrong.>>This is a major problem in administering my members. Is there a hidden setting that I can make to fix this bad behavior?>You're describing a lotta problems here. Take one at a time and get help solving it before working on the next.Glenn-------------------------------------------------------------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/ Glenn Busbin

DOWNLOAD WEBDNA NOW!

Re: db caching in bizarre ways

2001

Top Articles:

Related Readings: