Re: hidden databases

This WebDNA talk-list message is from

2000


It keeps the original formatting.
numero = 36214
interpreted = N
texte = >I was going over the archives and I found some one else had a similar >question, but it was for [writefile] >the solution was this code: >[writefile secure=f][/writefile] When webcat appends to a db, or closes or commits the db, it also changes the creator to WWW‡. That's what prevents webstar ftp from being able to 'see' the file, because webstar ftp is not a full-featured ftp server -- it cannot 'see' or download WWW‡ files like a normal ftp server can.But there's a webcat-based work-around:1- Create a separate upload folder for all your newly-uploaded db files. 2- Create a special admin template that closes the old database file, then immediately moves the newly-uploaded file to the location of the old file, thus forcing the old file to be overwritten by the new one.This technique is guaranteed to force webcat to purge the dbName.db file from its RAM cache, so when the new database file overwrites the old one, it's the NEW file that gets loaded into webcat's RAM cache.This is necessary because if you do *not* purge webcat's RAM-cached database immediately before overwriting that file on disk, then webcat will end up overwriting the new file with the *old* RAM-cached data the next time it commits its RAM-cached data to disk -- and that's not what you want at all ... ================================ Kenneth Grome, WebDNA Consultant 808-737-6499 http://webdna.net ================================------------------------------------------------------------- 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: hidden databases (Arturo Vargas 2000)
  2. Re: hidden databases (Kenneth Grome 2000)
  3. Re: hidden databases (Arturo Vargas 2000)
  4. Re: hidden databases (Kenneth Grome 2000)
  5. Re: hidden databases (Paul Uttermohlen 2000)
  6. Re: hidden databases (Arturo Vargas 2000)
  7. Re: hidden databases (Paul Fowler 2000)
  8. Re: hidden databases (WebDNA Support 2000)
  9. Re: hidden databases (Arturo Vargas 2000)
  10. Re: hidden databases (WebDNA Support 2000)
  11. hidden databases (Arturo Vargas 2000)
  12. Re: hidden databases (Mark Derrick 2000)
  13. Re: hidden databases (Bob Sneidar 2000)
  14. Re: hidden databases (Bob Sneidar 2000)
  15. Re: hidden databases (Alex McCombie 2000)
  16. WebStar Directory Indexer (was:Re: hidden databases) (Mark Derrick 2000)
  17. Re: hidden databases (Mark Derrick 2000)
  18. Re: hidden databases (Brian Boegershausen 2000)
  19. Re: hidden databases (WebDNA Support 2000)
  20. Re: hidden databases (Robert Wade 2000)
  21. Re: hidden databases (Jesse Proudman (Lists Account) 2000)
  22. Re: hidden databases (Robert Wade 2000)
  23. Re: hidden databases (Arturo Vargas 2000)
  24. Re: hidden databases (Robert Wade 2000)
  25. Re: hidden databases (Jesse Proudman 2000)
  26. hidden databases (Arturo Vargas 2000)
>I was going over the archives and I found some one else had a similar >question, but it was for [writefile] >the solution was this code: >[writefile secure=f][/writefile] When webcat appends to a db, or closes or commits the db, it also changes the creator to WWW‡. That's what prevents webstar ftp from being able to 'see' the file, because webstar ftp is not a full-featured ftp server -- it cannot 'see' or download WWW‡ files like a normal ftp server can.But there's a webcat-based work-around:1- Create a separate upload folder for all your newly-uploaded db files. 2- Create a special admin template that closes the old database file, then immediately moves the newly-uploaded file to the location of the old file, thus forcing the old file to be overwritten by the new one.This technique is guaranteed to force webcat to purge the dbName.db file from its RAM cache, so when the new database file overwrites the old one, it's the NEW file that gets loaded into webcat's RAM cache.This is necessary because if you do *not* purge webcat's RAM-cached database immediately before overwriting that file on disk, then webcat will end up overwriting the new file with the *old* RAM-cached data the next time it commits its RAM-cached data to disk -- and that's not what you want at all ... ================================ Kenneth Grome, WebDNA Consultant 808-737-6499 http://webdna.net ================================------------------------------------------------------------- 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/ 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:

Generating unique SKU from [cart] - FIXED! (1997) WebCat2 Append problem (B14Macacgi) (1997) Help- WebCat won't parse pages! (2002) Web Catalog 2 demo (1997) WebCatalog Hosting (1996) webDNA and ASP pages (1997) Sku numbers (1997) Email within tmpl ? (1997) Possible Macv2.1b2 Merge Bug (1997) WCS Newbie question (1997) Help formatting search results w/ table (1997) Almost a there but..bye bye NetCloak (1997) ThreadMem ignored? (1998) Cart Number sequence (1997) WebDNA-Talk Digest mode broken (1997) HEADER AND FOOTER (1997) WebCatalog for guestbook ? (1997) syntax question, not in online refernce (1997) Webmerchant PC auth (1998) WebCat2b13MacPlugIn - [include] doesn't allow creator (1997)