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

This WebDNA talk-list message is from

2015


It keeps the original formatting.
numero = 112076
interpreted = N
texte = I have an idea.. let=92s publicly spend resources rewriting the WebDNA = engine with basic tags and contexts that do things we already easily have the ability to do, but with less power and different names. Donovan On Feb 6, 2015, at 6:18 AM, Kenneth Grome = wrote: >> A default "central" reserved.db is not a bad idea (could be=20 >> stored inside /WebDNA folder) ... >=20 > I agree. I think the default location of reserved.db should be > the /WebDNA folder since this is where all the other required db > files are stored, at least in the FastCGI version. >=20 >=20 >> but it would store all the information for the website which=20 >> could make it big and difficult to handle ... >=20 > Why would it matter if the same volume of data were stored in a > single db or in separate dbs? It's still the same amount of data > either way. Or will the reserved.db work differently than our > other dbs? >=20 > One thing that actually SHOULD work differently is that this db > should ignore the prefs and be flushed to disk every time [store] > is used. Otherwise newly stored values might be lost. >=20 >=20 >> Then we will anyway have [store=20 >> path=3D../../admin/reserved.db]var1=3DJoe[/store] and [recall=20 >> var1&path=3D../../admin/reserved.db] to add flexibility. >=20 > Exactly! But here's another way to add similar flexibility: >=20 > Use these tags for the default server-wide scope: >=20 > [store]var1=3DJoe[/store] > [recall var1] >=20 > Then use these for local scope which will default to using the > reserved.db in the same folder: >=20 > [localStore]var1=3DJoe[/localStore] > [localRecall var1] >=20 > Then if you really want to be flexible, allow the path option to > be used in these "local scope" tags like this: >=20 > [localStore path=3Da/b/c/reserved.db]var1=3DJoe[/localStore] > [localRecall name=3Dvar1&path=3Da/b/c/reserved.db] >=20 > But never allow the path option in the default [store] and > [recall] tags -- because the default reserved.db will always be > located in the /WebDNA folder, or in the location specified in the > preference file which in this case is webdna.ini. >=20 > Using this approach means we have the flexibility to move our > default reserved.db file somewhere else other than the /WebDNA > folder, but there will still be only one default reserved.db file > for 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 no > path is specified, or optionally location specified by the path > parameter. >=20 > :) >=20 > Regards, > Kenneth Grome > WebDNA Solutions > http://www.webdnasolutions.com > Web Database Systems and Linux Server Management >=20 > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] [store] and [recall]: default db location (WebDNA TPP 2015)
  2. Re: [WebDNA] [store] and [recall]: default db location (Terry Wilson 2015)
  3. Re: [WebDNA] [store] and [recall]: default db location (Donovan Brooke 2015)
  4. Re: [WebDNA] [store] and [recall]: default db location (Donovan Brooke 2015)
  5. Re: [WebDNA] [store] and [recall]: default db location (Donovan Brooke 2015)
  6. Re: [WebDNA] [store] and [recall]: default db location (christophe.billiottet@webdna.us 2015)
  7. Re: [WebDNA] [store] and [recall]: default db location (Kenneth Grome 2015)
  8. Re: [WebDNA] [store] and [recall]: default db location (christophe.billiottet@webdna.us 2015)
  9. [WebDNA] [store] and [recall]: default db location (Kenneth Grome 2015)
I have an idea.. let=92s publicly spend resources rewriting the WebDNA = engine with basic tags and contexts that do things we already easily have the ability to do, but with less power and different names. Donovan On Feb 6, 2015, at 6:18 AM, Kenneth Grome = wrote: >> A default "central" reserved.db is not a bad idea (could be=20 >> stored inside /WebDNA folder) ... >=20 > I agree. I think the default location of reserved.db should be > the /WebDNA folder since this is where all the other required db > files are stored, at least in the FastCGI version. >=20 >=20 >> but it would store all the information for the website which=20 >> could make it big and difficult to handle ... >=20 > Why would it matter if the same volume of data were stored in a > single db or in separate dbs? It's still the same amount of data > either way. Or will the reserved.db work differently than our > other dbs? >=20 > One thing that actually SHOULD work differently is that this db > should ignore the prefs and be flushed to disk every time [store] > is used. Otherwise newly stored values might be lost. >=20 >=20 >> Then we will anyway have [store=20 >> path=3D../../admin/reserved.db]var1=3DJoe[/store] and [recall=20 >> var1&path=3D../../admin/reserved.db] to add flexibility. >=20 > Exactly! But here's another way to add similar flexibility: >=20 > Use these tags for the default server-wide scope: >=20 > [store]var1=3DJoe[/store] > [recall var1] >=20 > Then use these for local scope which will default to using the > reserved.db in the same folder: >=20 > [localStore]var1=3DJoe[/localStore] > [localRecall var1] >=20 > Then if you really want to be flexible, allow the path option to > be used in these "local scope" tags like this: >=20 > [localStore path=3Da/b/c/reserved.db]var1=3DJoe[/localStore] > [localRecall name=3Dvar1&path=3Da/b/c/reserved.db] >=20 > But never allow the path option in the default [store] and > [recall] tags -- because the default reserved.db will always be > located in the /WebDNA folder, or in the location specified in the > preference file which in this case is webdna.ini. >=20 > Using this approach means we have the flexibility to move our > default reserved.db file somewhere else other than the /WebDNA > folder, but there will still be only one default reserved.db file > for 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 no > path is specified, or optionally location specified by the path > parameter. >=20 > :) >=20 > Regards, > Kenneth Grome > WebDNA Solutions > http://www.webdnasolutions.com > Web Database Systems and Linux Server Management >=20 > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us Donovan Brooke

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:

WebCat cannot handle compatible search parameters? (1997) Feature Request: [moverecord] (2003) Can you do this??? and other stuff (1997) NT Manual (1997) unable to launch acgi in WebCat (1997) File Uploads (1998) RE: Answer: WebDelivery downloads alias, not original ? (1997) 2.0 Info (1997) Email...Thanks (1997) WebCat2 - Getting to the browser's username/password data (1997) Search/sort in URL Was: GuestBook example (1997) Permission denied? (2004) Stumpted Again (1997) Online reference (1997) [referrer] tag (1997) Cookies (1999) summarizing multiple fields (2000) WebTen? (1997) Design Help Needed (1998) text variables... weigh much? (2004)