store
[store] is a simple context that stores variables permanently
The process would use [store] and [recall] the name of the variable the variable itself
The variable and the name are as long as requested: it save the hassle of writing the code to store those in a database. However, to avoid "overheating", we can have only one name per variable, meaning that if we store name3 as "pink", and later store name3 as "black", then only the last value will remain and "pink" will be overwritten by "black"
Example WebDNA code:
[store]var1=Joe[/store]
The data is recorded inside a database "reserved.db" in /WebDNA (FastCGI version), in /globals/ (server version, no sandboxing) or in /SandBoxes/domain.com/Globals/ (server version with sandboxing), one column for the variable name and the other one for the string.
If reserved.db does not exist, it will be created automatically and transparently.
To recover your data, you can use either
The data is usable anytime, anywhere: you can store data with one browser and someone else can recall it with another browser.
Fred says Today is 04/17/2015
The variable and the name are as long as requested: it save the hassle of writing the code to store those in a database. However, to avoid "overheating", we can have only one name per variable, meaning that if we store name3 as "pink", and later store name3 as "black", then only the last value will remain and "pink" will be overwritten by "black"
Example WebDNA code:
[store]var1=Joe[/store]
The data is recorded inside a database "reserved.db" in /WebDNA (FastCGI version), in /globals/ (server version, no sandboxing) or in /SandBoxes/domain.com/Globals/ (server version with sandboxing), one column for the variable name and the other one for the string.
If reserved.db does not exist, it will be created automatically and transparently.
| Parameter | Description |
|---|---|
| show | (optional) "T" or "F". Default behavior is to hide the value when assigning to a variable. If we want the value to be shown at the same time it is assigned to a variable, we may set Show=T (There is no reason to ever use show=f, as this is default behavior.) Example WebDNA code: [store show=T]var1=Joe[/store] |
| multi | (optional) "T" or "F". Allows to assign more than one text variable in a single context. Example WebDNA code: [store multi=T]var1=Joe&var2=Fred[/store] simultaneously assigns the two variables. (There is no need to use multi=f for single variables.) |
| path | (optional) path of the database, if a user wants to use another database than the default one. Example WebDNA code: [store path=../../specific.db]var1=Joe[/store] Look for "specific.db" two level up |
| parse | (optional) "T" or "F". Interpret o no the tags that would be in the data to be stored. Example WebDNA code: would give Example WebDNA code: would give The defaut behavior being parse=F |
To recover your data, you can use either
[recall var1] and get the tag replaced by the variable.
[recall var1&path=../../specific.db] or [recall path=../../specific.db&var1]The data is usable anytime, anywhere: you can store data with one browser and someone else can recall it with another browser.
You can also use [convertwords] [/convertwords]
[convertwords path=../../specific.db]
var2 says var1
[/convertwords]
Fred says Today is 04/17/2015