Re: Issues with the default db files ...

This WebDNA talk-list message is from

2003


It keeps the original formatting.
numero = 49211
interpreted = N
texte = Ken,Glad to see that you have an interest in 5.0 after all.Scott would be the expert on Sandboxes, so I'll leave the technical answer to him ...Phil B.-----Original Message----- From: Kenneth Grome To: WebDNA-Talk@talk.smithmicro.com Sent: 4/5/03 12:26 AM Subject: Issues with the default db files ...Ever since this software has existed, the default behavior has been that we could refer to certain db files WITHOUT having to use the actual path to those files.In fact, it has never mattered if the path was wrong, because the webdna software has always 'corrected' the bad path to these db files. The files I'm referring to are:WebCatalog Prefs users.db standardconversions.db errormessages.db triggers.dbThese db's apparently have their paths hard-coded into the engine. I learned this many years ago when I put a different users.db into a separate folder and referred to it via the proper path, but webcatalog insisted upon ignoring the path I gave it, and instead it followed the hard-coded path that's apparently built into th engine code. From what I recall, Grant explained this to me as some kind of anti-hacking feature.My question to SMSI is this:Now that there's going to be a separate set of the above files for each sandbox, what's going to happen to our old webdna code that does not use a path to these files when we try to use that code on v5?Will it still work like before, except that now it will reference the above files in the current sandbox?Or will it break because now it doesn't know which file we are referring to since those files are not defined by a specific file path? -- Sincerely, Kenneth GromePS: My email address is kengrome@softhome.net until further notice.------------------------------------------------------------- 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:

    
  1. Re: Issues with the default db files ... (Scott Anderson 2003)
  2. Re: Issues with the default db files ... (Kenneth Grome 2003)
  3. Re: Issues with the default db files ... (Alain Russell 2003)
  4. Re: Issues with the default db files ... (Scott Anderson 2003)
  5. Re: Issues with the default db files ... (Phillip Bonesteele 2003)
  6. Re: Issues with the default db files ... (Kenneth Grome 2003)
  7. Re: Issues with the default db files ... (Alain Russell 2003)
  8. Issues with the default db files ... (Kenneth Grome 2003)
Ken,Glad to see that you have an interest in 5.0 after all.Scott would be the expert on Sandboxes, so I'll leave the technical answer to him ...Phil B.-----Original Message----- From: Kenneth Grome To: WebDNA-Talk@talk.smithmicro.com Sent: 4/5/03 12:26 AM Subject: Issues with the default db files ...Ever since this software has existed, the default behavior has been that we could refer to certain db files WITHOUT having to use the actual path to those files.In fact, it has never mattered if the path was wrong, because the webdna software has always 'corrected' the bad path to these db files. The files I'm referring to are:WebCatalog Prefs users.db standardconversions.db errormessages.db triggers.dbThese db's apparently have their paths hard-coded into the engine. I learned this many years ago when I put a different users.db into a separate folder and referred to it via the proper path, but webcatalog insisted upon ignoring the path I gave it, and instead it followed the hard-coded path that's apparently built into th engine code. From what I recall, Grant explained this to me as some kind of anti-hacking feature.My question to SMSI is this:Now that there's going to be a separate set of the above files for each sandbox, what's going to happen to our old webdna code that does not use a path to these files when we try to use that code on v5?Will it still work like before, except that now it will reference the above files in the current sandbox?Or will it break because now it doesn't know which file we are referring to since those files are not defined by a specific file path? -- Sincerely, Kenneth GromePS: My email address is kengrome@softhome.net until further notice.------------------------------------------------------------- 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/ Phillip Bonesteele

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:

Searching multiple Databases (1997) Separate SSL Server (1997) Re:2nd WebCatalog2 Feature Request (1996) External Images (1998) WebCat shared memory? (1999) RE: [WebDNA] Use of MySQL with WebDNA (2010) action=add works with IE but not Communicator (2000) Upload files script (2003) japanese characters (1997) RE: WebCat 3.0 Serial Numbers (1999) Uploading out of FMP (2001) Passing Cart variable to subdirectory files? (1997) text size limitation (1997) What file? (1997) Live Webcasts (1999) WebCat2b13MacPlugin - nested [xxx] contexts (1997) The Form authentication trick (2000) calculating tax rates, mail order solutions and version 2 (1997) Shipcost lookup? (1997) Dynamic Image Generation (2000)