Re: [WebDNA] [store] and [recall]: default db location

This WebDNA talk-list message is from

2015

It keeps the original formatting. numero = 112072
interpreted = N
texte = > A default "central" reserved.db is not a bad idea (could be > stored inside /WebDNA folder) ...I agree. I think the default location of reserved.db should bethe /WebDNA folder since this is where all the other required dbfiles are stored, at least in the FastCGI version.> but it would store all the information for the website which > could make it big and difficult to handle ...Why would it matter if the same volume of data were stored in asingle db or in separate dbs? It's still the same amount of dataeither way. Or will the reserved.db work differently than ourother dbs?One thing that actually SHOULD work differently is that this dbshould ignore the prefs and be flushed to disk every time [store]is used. Otherwise newly stored values might be lost.> Then we will anyway have [store > path=../../admin/reserved.db]var1=Joe[/store] and [recall > var1&path=../../admin/reserved.db] to add flexibility.Exactly! But here's another way to add similar flexibility:Use these tags for the default server-wide scope:[store]var1=Joe[/store][recall var1]Then use these for local scope which will default to using thereserved.db in the same folder:[localStore]var1=Joe[/localStore][localRecall var1]Then if you really want to be flexible, allow the path option tobe used in these "local scope" tags like this:[localStore path=a/b/c/reserved.db]var1=Joe[/localStore][localRecall name=var1&path=a/b/c/reserved.db]But never allow the path option in the default [store] and[recall] tags -- because the default reserved.db will always belocated in the /WebDNA folder, or in the location specified in thepreference file which in this case is webdna.ini.Using this approach means we have the flexibility to move ourdefault reserved.db file somewhere else other than the /WebDNAfolder, but there will still be only one default reserved.db filefor WebDNA to deal with when it encounters [store] and [recall].Any other reserved.db files will be referenced by [localstore] and[localrecall] and their locations will be the same folder when nopath is specified, or optionally location specified by the pathparameter.:)Regards,Kenneth GromeWebDNA Solutionshttp://www.webdnasolutions.comWeb Database Systems and Linux Server Management Associated Messages, from the most recent to the oldest:

Re: [WebDNA] [store] and [recall]: default db location (WebDNA TPP 2015) Re: [WebDNA] [store] and [recall]: default db location (Terry Wilson 2015) Re: [WebDNA] [store] and [recall]: default db location (Donovan Brooke 2015) Re: [WebDNA] [store] and [recall]: default db location (Donovan Brooke 2015) Re: [WebDNA] [store] and [recall]: default db location (Donovan Brooke 2015) Re: [WebDNA] [store] and [recall]: default db location (christophe.billiottet@webdna.us 2015) Re: [WebDNA] [store] and [recall]: default db location (Kenneth Grome 2015) Re: [WebDNA] [store] and [recall]: default db location (christophe.billiottet@webdna.us 2015) [WebDNA] [store] and [recall]: default db location (Kenneth Grome 2015)

> A default "central" reserved.db is not a bad idea (could be > stored inside /WebDNA folder) ...I agree. I think the default location of reserved.db should bethe /WebDNA folder since this is where all the other required dbfiles are stored, at least in the FastCGI version.> but it would store all the information for the website which > could make it big and difficult to handle ...Why would it matter if the same volume of data were stored in asingle db or in separate dbs? It's still the same amount of dataeither way. Or will the reserved.db work differently than ourother dbs?One thing that actually SHOULD work differently is that this dbshould ignore the prefs and be flushed to disk every time [store]is used. Otherwise newly stored values might be lost.> Then we will anyway have [store > path=../../admin/reserved.db]var1=Joe[/store] and [recall > var1&path=../../admin/reserved.db] to add flexibility.Exactly! But here's another way to add similar flexibility:Use these tags for the default server-wide scope:[store]var1=Joe[/store][recall var1]Then use these for local scope which will default to using thereserved.db in the same folder:[localStore]var1=Joe[/localStore][localRecall var1]Then if you really want to be flexible, allow the path option tobe used in these "local scope" tags like this:[localStore path=a/b/c/reserved.db]var1=Joe[/localStore][localRecall name=var1&path=a/b/c/reserved.db]But never allow the path option in the default [store] and[recall] tags -- because the default reserved.db will always belocated in the /WebDNA folder, or in the location specified in thepreference file which in this case is webdna.ini.Using this approach means we have the flexibility to move ourdefault reserved.db file somewhere else other than the /WebDNAfolder, but there will still be only one default reserved.db filefor WebDNA to deal with when it encounters [store] and [recall].Any other reserved.db files will be referenced by [localstore] and[localrecall] and their locations will be the same folder when nopath is specified, or optionally location specified by the pathparameter.:)Regards,Kenneth GromeWebDNA Solutionshttp://www.webdnasolutions.comWeb Database Systems and Linux Server Management 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:

Restart of DBserver (1997) Encyption mail was Suggestions for Topics ... (1998) Hosts who have upgraded to v5.0? (2003) Interpreting WebDNA tags (2004) WebCatalog can't find database (1997) Can I invoke an ssi plugin from within a webcat page (1997) A good idea? (1998) Are Talk List Archives off line (2000) Cart Numbers (1997) WebCommerce: Folder organization ? (1997) hmmm (2006) Date format problems (1997) Max Record length restated as maybe bug (1997) Folder Follies (1998) WebCatalog2 Feature Feedback (1996) WebTen and WebCat (1997) Sorry I didn't pay attention-but ??? (1997) LOOP and IF statements (1997) CC: (1998) Ampersand (1997)