Variables
The core of addedValues is the definition of each variable that makes up your database.
It is naturally the starting point of everything. It should also become automatic... If your are contemplating a structural change to your site, you should first consider whether a variable needs modifying...
Some helpful pointers...
- Get as many of your variables defined before you start loading data. This is even more true for variables that will require indexing (those upon which you will conduct searches).
- Make sure that your variable type is well defined. Why? because changing it can be resource and time consuming. You can, for example, have your postal code or phone number registered as an integer. But then you decide to have an additional control feature whereby you use regex to check for patterns (i.e. Canadian postal codes go alpha-num-alpha-space-num-alpha-num) to avoid input errors. This change won't happen by simply snapping your fingers; more info here.
- The larger your database, the greater the impact of any change... Adding a new indexed variable with 5000 records already loaded means a lot of work behind the scenes and an assurance that you are a patient wo/man. Records have to be matched against the original record, data must be validated, then properly indexed and sorted... Frontier itself, in the background, slows down over time due to its memory management issues. Thus, careful planning is your best investment; you will save significant amounts of time !